Main ran the plugin-order check in the code-splitter plugin, so only with
`autoCodeSplitting` on; the single compiler plugin ran it in every mode and
failed the router-monorepo example builds (`react()` before
`tanstackRouter()`, splitting off). Without splitting, route HMR works
whatever the order: the HMR block is appended to what the framework plugin
emitted. Verified on a real page (integration/route-hmr-browser-plugin-
order.test.ts): with the framework plugin first and splitting off, an edit
of a named or inline React component shows in place keeping its state, a
Solid edit shows in place, no warning; with splitting on, the dev server
refuses to start. The six example reorders are reverted: main's order builds
again, and the example builds of the PR workflow cover the restored gate.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The branch's compiler plugin checks the plugin order in every mode (main only did with autoCodeSplitting on), so these six library builds failed with "Plugin order error: '@vitejs/plugin-react' is placed before '@tanstack/router-plugin'".
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Brings in Node 26.12.1, Version Packages (#8745), the TanStack Markdown
rendering guide (#8808) and the Nx 24 upgrade (#8807). Conflicts were
limited to a version bump in the Solid Rspack quickstart example and
pnpm-lock.yaml, which was regenerated with pnpm install.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- esbuild: autoCodeSplitting is refused; the esbuild installation docs
and quickstart examples no longer enable it
- automatic code splitting: callbacks reading this stay unsplit; route
CSS moves with the split components only when all are split
- Start: server functions only server code calls are not HTTP-callable
in production (dev answers and warns); generateFunctionId arguments
and the default ids; onViolation timing in builds; route CSS loading
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(deps): bump srvx to ^1.0.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(deps): bump @vitejs/plugin-rsc to ^0.5.37
0.5.37 depends on srvx ^1.0.5, which drops the last srvx 0.11 copy from
the lockfile. It is temporarily excluded from minimumReleaseAge until it
is 24h old.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: drop minimumReleaseAge exclusion for @vitejs/plugin-rsc
0.5.37 is now older than the 24h minimum release age.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(ci): TEMP experiment - rsc e2e on srvx 0.10 (revert before merge)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Revert "test(ci): TEMP experiment - rsc e2e on srvx 0.10 (revert before merge)"
This reverts commit 2c7279a0b9.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(start): preserve dev SSR CSS order
fixes#7794
* add e2e tests for solid and vue, handle vue style urls
* test(start): cover bundled dev styles and SSR reload lifecycle
* fix(start): use completed bundled graph for dev SSR styles
* fix(start): preserve import reachability across bundled dev variants
* test(start): cover layered inline CSS without build observers
* test(start): wait for bundled HMR route registration
* test(start): await HMR readiness in both Vite modes
* test(start): trace initial bundled HMR update in CI
* test(start): trace native bundled HMR watcher in CI
* test(start): inspect initial native watch registrations
* fix(start): support the latest bundled dev toolchain