Repository navigation
feat!: extract independently versioned BTST plugin packages for v6 - #335
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…tegration # Conflicts: # packages/stack/registry/btst-blog.json
Contributor
Bundle size322 of 339 bundles changed.
Showing the 10 largest changes by absolute gzip bytes. Unavailable:
Measured 22 packed archives separately; full report includes their compressed bytes without installed dependencies. |
…ackage # Conflicts: # packages/cli/src/utils/__tests__/scaffold-plan.test.ts
Prepare Core v6 and independent plugins beta
Add matched v5/v6 rendering benchmarks and report checks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extract all 19 built-in plugins into independent packages and keep
@btst/stackas the shared Core v6 runtime. Preserve routes, IDs, authorization, data, ESM/CommonJS and SSR/SSG contracts. Optional standalone APIs move to@btst/components; Blog–Newsletter integration is opt-in, and page context no longer requires AI Chat.This is the published beta implementation. Stable promotion #349 advances Core/CLI to 6.0.0 and plugins/Components to 1.0.0 after real-consumer validation. The migration guide maps all 157 baseline public imports. Core ships no legacy feature/component facade or corresponding dependencies.
Evidence
Verification limits: API-key-dependent local cases skip without configured credentials; CI uses its configured provider key. Existing registry peer/type exceptions remain explicit. The production smoke is read-only; authenticated/provider writes ran against the isolated local application. Preview auth CORS predates this migration and does not occur on the production domain. Mail delivery, Firecrawl and payment-provider calls were not exercised by the web migration checks.
Merge Danger
Door: two-way
Source changes can be reverted. Core v6 requires the documented import migration; database identities and existing data are preserved. Published npm versions are immutable.
Blast Radius: consumers
Applications, CLI scaffolding, registry consumers and release automation use the new ownership boundaries. Stable publication and a stable-pin web follow-up remain coordinated in #349.
Closes #310
Closes #311
Closes #312
Closes #313
Closes #314
Closes #315
Closes #316
Closes #317
Closes #318
Closes #319
Closes #320
Closes #321
Closes #322
Closes #323
Closes #324
Closes #325
Closes #326
Closes #327
Closes #328
Closes #329
Closes #330
Closes #331
Closes #332
Closes #333
Closes #334