Repository navigation
BTST v6.0.0-beta.0
Pre-releaseBTST v6 is available as a beta on npm's next channel. Existing stable Core and CLI releases remain on latest.
pnpm dlx @btst/codegen@next init| Package | Beta |
|---|---|
@btst/stack, @btst/codegen |
6.0.0-beta.0 |
All 19 @btst/plugin-* packages |
1.0.0-beta.0 |
Optional @btst/components |
1.0.0-beta.0 |
Optional @btst/better-auth-ui |
3.0.3-beta.0 |
Core owns the shared runtime; selected features have independent package ownership. The CLI pins the compatible installation set and required registrations. Existing applications must migrate feature imports; routes, permissions, query/data identities and stored data are preserved. See the beta migration guide.
Matched rendering measurements
15 alternating paired runs compared published v5.2.0 with the exact beta candidate in matching Next.js 16.4.5 / React 19.3.1 production applications. All 330 measured observations passed. Profile: 4× browser CPU slowdown, 150 ms latency, 1.6 Mbit/s download, 1280×800 viewport; servers were warm and cold browsers used fresh caches.
| Scenario | Cold LCP, v5 → beta | Actual route readiness, v5 → beta |
|---|---|---|
| Core shell | 1.836 → 0.660 s | 1.904 → 1.372 s |
| Blog reader | 3.488 → 0.976 s | 3.506 → 2.949 s |
| Blog editor | 2.660 → 0.996 s | 6.045 → 5.242 s |
| Multi-plugin dashboard | 2.376 → 0.668 s | 2.485 → 1.903 s |
The principal observed transfer change is smaller CSS under the matched Tailwind source scan; JavaScript transfer is roughly flat. This is consistent with feature/package isolation and is not a separate causal ablation. Warm-cache results are mixed, all client-navigation comparisons are inconclusive, and two frame-readiness proxies regress by about 2 ms. No field-INP, universal rendering or server-rendering speedup is claimed. The controlled common Lucide override differs from the CLI's separately validated dependency cohort.
The attached rendering report ZIP includes a standalone HTML report, charts, raw observations, confidence intervals, acceptance checks, traces, screenshots, lockfiles and build logs. Reproducible benchmark harness.
Verification
The release gate requires all expected CI jobs and both previews on the exact candidate, with consistent repeated observations immediately before publication. Strict npm/pnpm packed-consumer checks, all three framework suites, source/version/channel/integrity checks, and preserved stable tags are part of this rollout. Benchmark/source review findings are resolved.
Beta source: ac7a6206d81e36262baf4392255575b4dc9bf6b5. Auth companion source: cdb0a0fa773ad4f90a67848d97558582e7ab7486. Publication is from the beta branches. Source integration: v6 refactor PR, beta preparation, benchmark harness.