Skip to content

feat: isolate adapters via subpaths and harden npm publish - #1

Merged
MohammadTahaBatoomi merged 1 commit into
devfrom
feature/adapter-subpaths-v1.5.0
Sep 19, 2026
Merged

MohammadTahaBatoomi merged 1 commit into
devfrom
feature/adapter-subpaths-v1.5.0

Conversation

@MohammadTahaBatoomi

Copy link
Copy Markdown
Member

Split framework adapters into separate package exports so the core entry no longer requires Next.js or other peers at import time. Gate CI publish to main-only pushes and ship a lean tarball with an explicit files allowlist.

What does this PR do?

Briefly describe the change and why it's needed.

Closes # (if applicable)

Type of change

  • Bug fix
  • New feature
  • Documentation update
  • Chore / tooling / CI
  • Refactor (no functional change)

Checklist

  • I've read CONTRIBUTING.md
  • Linter passes (pnpm lint / make lint)
  • Build passes (pnpm build / make build-app)
  • Tests added/updated, if applicable
  • Docs updated, if applicable
  • No secrets, .env files, or credentials included in this PR

Screenshots (if UI change)

Additional notes

Anything reviewers should know — tricky parts, follow-up work, etc.

Split framework adapters into separate package exports so the core entry
no longer requires Next.js or other peers at import time. Gate CI publish
to main-only pushes and ship a lean tarball with an explicit files allowlist.

Co-authored-by: Cursor <cursoragent@cursor.com>
@MohammadTahaBatoomi
MohammadTahaBatoomi merged commit 7d07fad into dev Sep 19, 2026
1 check passed
@MohammadTahaBatoomi
MohammadTahaBatoomi deleted the feature/adapter-subpaths-v1.5.0 branch September 19, 2026 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant