0
Fork 0
mirror of https://github.com/TanStack/router.git synced 2026-11-16 19:38:07 +00:00
Commit graph

776 commits

Author SHA1 Message Date
Brenley Dueck
df8839d83f
Upgrade solid-js to 2.0.0-rc.0 and rename vite-plugin-solid to @solidjs/vite-plugin (#8058) 2026-08-13 12:07:49 +02:00
github-actions[bot]
03fd7365a7
ci: Version Packages (beta) (#8034)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-08-10 15:24:58 -05:00
Brenley Dueck
980ed5794a
Upgrade solidjs beta 32 (#8014)
* Upgrade solid-js to 2.0.0-beta.32 and vite-plugin-solid to 3.0.0-next.23

- solid-js / @solidjs/web / babel-preset-solid: 2.0.0-beta.29 -> 2.0.0-beta.32
- vite-plugin-solid: ^3.0.0-next.21 -> ^3.0.0-next.23 (ships @dom-expressions/compiler 0.50.0-next.40)
- Migrate server tests off removed renderToStringAsync: awaiting renderToStream()
  now resolves with the fully-settled HTML string

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci: apply automated fixes

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-08-10 15:05:00 -05:00
Ryan Carniato
41cffa00f3
fix(solid-router): make the global loading boundary opt-in and server/client-symmetric (#8027)
* fix(solid-router): make the global loading boundary opt-in and server/client-symmetric

`Matches` wrapped the match tree in a client-only `Solid.Loading`
boundary unless `disableGlobalCatchBoundary`, `isServer`, or
`router.ssr` was set, while the server side always rendered
`SafeFragment`. Apps that server-render without the `$_TSR` stream
protocol (own server entry: memory history, awaited `router.load()`,
`renderToStream`) never set `router.ssr`, so the client hydrated a
boundary the server never rendered. That desyncs Solid's positional
node claiming and surfaces as an opaque `reconcileArrays` crash
(`NotFoundError: insertBefore`).

The wrapper is now opt-in and the decision is evaluated identically on
the server and the client. It renders only when all of these hold:

- the app configured root pending UI (root `pendingComponent` or
  `defaultPendingComponent`) — new;
- `router.ssr` is not set (the `$_TSR` protocol short-circuit,
  unchanged and pinned by tests);
- `disableGlobalCatchBoundary` is not set (unchanged).

There is no `isServer` arm, no hydration probe, and no match-state
inspection — the decision reads only router configuration, so the
server tree and the hydrating client tree cannot disagree.

With nothing configured there is no wrapper at all: pending propagates
as ordinary Solid 2 async. The previous behavior there was an invisible
`Solid.Loading` with a `null` fallback, which also converted errors to
pending. With pending UI configured, the boundary now renders on both
sides, so external SSR hydrates cleanly (server nodes claimed and
reused, no pending flash) and the pending UI keeps working for
post-hydration navigations — a client-only wrapper, even a settled one,
shifts hydration-key derivation and leaves the server nodes unclaimed.

Tests: matches-hydration-boundary.test.tsx pins the opt-in decision,
the protocol short-circuit, `disableGlobalCatchBoundary`, and that the
decision is identical whether or not a hydration pass is in flight (a
hydration-keyed decision would freeze `SafeFragment` into hydrated apps
permanently); server-mode matchesLoadingBoundary.test.tsx pins the
symmetric server output. Verified additionally against a real
`renderToString` -> `hydrate` round trip: zero hydration errors, zero
unclaimed nodes, server DOM reused by identity.

Co-authored-by: Cursor <cursoragent@cursor.com>

* ci: apply automated fixes

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-08-10 15:03:44 -05:00
Brenley Dueck
99756c0710 fix(solid-start): resolve SSR'd lazy() client assets via vite-plugin-solid's manifest
Solid 2's streaming renderer resolves the modules behind server-rendered
lazy() boundaries through its `manifest` render option: it emits stylesheet
links and modulepreloads for the lazy chunk and serializes the module→asset
map the client needs to preload it before hydration. TanStack Start never
provided that manifest — its own start manifest is route-keyed and
intentionally excludes dynamic-import chunks — so direct visits to routes
with SSR'd lazy() components rendered without the lazy chunk's CSS and
logged "Asset manifest returned no client assets" on every request.
(Pre-merge this was masked: the old Match tree re-rendered the boundary
client-side after the failed hydration, fetching the CSS late via Vite's
dynamic-import helper.)

Wire up vite-plugin-solid's `virtual:solid-manifest` (dev module-graph
resolver in dev, the client build's `.vite/manifest.json` in builds), kept
entirely inside the solid packages:

- solid-router ships an inert `ssr/clientAssetsManifest` stub that the
  renderers prefer over the route-keyed manifest when non-undefined
- solid-start's vite plugin swaps the stub for `virtual:solid-manifest` in
  the server environment (with `isEntry` neutralized so Solid doesn't
  duplicate the entry stylesheet Start already emits) and enables
  `build.manifest` for the client build
- bundlers without the plugin (rsbuild) keep the stub and current behavior

Fixes the two shared-widget lazy-CSS tests in the solid-start
start-manifest e2e (10/10 passing; selective-ssr and basic suites verified
unaffected).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-05 13:10:36 -05:00
Brenley Dueck
e021c7a352 fix(solid-router): keep Transitioner hydration ids in sync between server and client
Solid 2 derives hydration keys from the reactive owner tree, and its server
onSettled stub consumes a child-id slot to mirror the client's effect owner.
The server early-return in Transitioner skipped that registration, shifting
every subsequent hydration key by one and causing a root-level hydration
mismatch that discarded the server-rendered HTML (breaking deferred/streaming
content and redirects in the solid-start e2e suites).

Run the same code on both sides again: the onSettled callback never executes
on the server, so only the owner-tree structure is shared.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-05 12:27:01 -05:00
Brenley Dueck
e958330a1d Merge branch 'main' into solid-router-v2-pre-main-merge-2
# Conflicts:
#	benchmarks/client-nav/package.json
#	e2e/solid-start/basic-auth/package.json
#	e2e/solid-start/basic-solid-query/package.json
#	e2e/solid-start/basic-tsr-config/package.json
#	e2e/solid-start/csp/package.json
#	e2e/solid-start/query-integration/package.json
#	e2e/solid-start/query-integration/src/routeTree.gen.ts
#	e2e/solid-start/scroll-restoration/package.json
#	e2e/solid-start/serialization-adapters/package.json
#	e2e/solid-start/server-functions/package.json
#	e2e/solid-start/server-routes/package.json
#	e2e/solid-start/virtual-routes/package.json
#	e2e/solid-start/website/package.json
#	examples/react/start-rscs/package.json
#	examples/solid/authenticated-routes-firebase/package.json
#	examples/solid/authenticated-routes/package.json
#	examples/solid/basic-default-search-params/package.json
#	examples/solid/basic-devtools-panel/package.json
#	examples/solid/basic-file-based/package.json
#	examples/solid/basic-non-nested-devtools/package.json
#	examples/solid/basic-solid-query-file-based/package.json
#	examples/solid/basic-solid-query/package.json
#	examples/solid/basic-ssr-file-based/package.json
#	examples/solid/basic-ssr-streaming-file-based/package.json
#	examples/solid/basic-virtual-file-based/package.json
#	examples/solid/basic-virtual-inside-file-based/package.json
#	examples/solid/basic/package.json
#	examples/solid/deferred-data/package.json
#	examples/solid/i18n-paraglide/package.json
#	examples/solid/kitchen-sink-file-based/package.json
#	examples/solid/kitchen-sink-solid-query-file-based/package.json
#	examples/solid/kitchen-sink-solid-query/package.json
#	examples/solid/kitchen-sink/package.json
#	examples/solid/large-file-based/package.json
#	examples/solid/location-masking/package.json
#	examples/solid/navigation-blocking/package.json
#	examples/solid/quickstart-esbuild-file-based/package.json
#	examples/solid/quickstart-file-based/package.json
#	examples/solid/quickstart-rspack-file-based/package.json
#	examples/solid/quickstart-webpack-file-based/package.json
#	examples/solid/quickstart/package.json
#	examples/solid/router-monorepo-simple-lazy/package.json
#	examples/solid/router-monorepo-simple-lazy/packages/app/package.json
#	examples/solid/router-monorepo-simple-lazy/packages/post-feature/package.json
#	examples/solid/router-monorepo-simple-lazy/packages/router/package.json
#	examples/solid/router-monorepo-simple/package.json
#	examples/solid/router-monorepo-simple/packages/app/package.json
#	examples/solid/router-monorepo-simple/packages/post-feature/package.json
#	examples/solid/router-monorepo-simple/packages/router/package.json
#	examples/solid/router-monorepo-solid-query/package.json
#	examples/solid/router-monorepo-solid-query/packages/app/package.json
#	examples/solid/router-monorepo-solid-query/packages/post-feature/package.json
#	examples/solid/router-monorepo-solid-query/packages/post-query/package.json
#	examples/solid/router-monorepo-solid-query/packages/router/package.json
#	examples/solid/scroll-restoration/package.json
#	examples/solid/search-validator-adapters/package.json
#	examples/solid/start-basic-auth/package.json
#	examples/solid/start-basic-authjs/package.json
#	examples/solid/start-basic-cloudflare/package.json
#	examples/solid/start-basic-netlify/package.json
#	examples/solid/start-basic-nitro/package.json
#	examples/solid/start-basic-solid-query/package.json
#	examples/solid/start-basic-static/package.json
#	examples/solid/start-basic/package.json
#	examples/solid/start-bun/package.json
#	examples/solid/start-convex-better-auth/package.json
#	examples/solid/start-counter/package.json
#	examples/solid/start-i18n-paraglide/package.json
#	examples/solid/start-large/package.json
#	examples/solid/start-streaming-data-from-server-functions/package.json
#	examples/solid/start-supabase-basic/package.json
#	examples/solid/start-tailwind-v4/package.json
#	examples/solid/view-transitions/package.json
#	examples/solid/with-framer-motion/package.json
#	examples/solid/with-trpc/package.json
#	packages/router-devtools-core/package.json
#	packages/solid-router-devtools/CHANGELOG.md
#	packages/solid-router-devtools/package.json
#	packages/solid-router/CHANGELOG.md
#	packages/solid-router/package.json
#	packages/solid-router/src/CatchBoundary.tsx
#	packages/solid-router/src/Match.tsx
#	packages/solid-router/src/Matches.tsx
#	packages/solid-router/src/Scripts.tsx
#	packages/solid-router/src/Transitioner.tsx
#	packages/solid-router/src/headContentUtils.tsx
#	packages/solid-router/src/lazyRouteComponent.tsx
#	packages/solid-router/src/link.tsx
#	packages/solid-router/src/routerStores.ts
#	packages/solid-router/src/ssr/RouterClient.tsx
#	packages/solid-router/src/useMatch.tsx
#	packages/solid-router/tests/link.test.tsx
#	packages/solid-router/tests/loaders.test.tsx
#	packages/solid-router/tests/routeContext.test.tsx
#	packages/solid-router/tests/store-updates-during-navigation.test.tsx
#	packages/solid-start-client/CHANGELOG.md
#	packages/solid-start-client/package.json
#	packages/solid-start-server/CHANGELOG.md
#	packages/solid-start-server/package.json
#	packages/solid-start/CHANGELOG.md
#	packages/solid-start/package.json
#	pnpm-lock.yaml
2026-08-04 21:59:13 -05:00
github-actions[bot]
704145c6d5
ci: Version Packages (#7946)
ci: changeset release

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-08-04 22:25:17 +02:00
Flo
45c4ad8d62
fix(router-core): lane match loader rewrite (#7805)
* fix: lane match loader rewrite

---------

Co-authored-by: Manuel Schiller <6340397+schiller-manuel@users.noreply.github.com>
2026-08-04 20:28:11 +02:00
Alem Tuzlak
b5e540d74a
docs: use the dynamic README header endpoint (#7940)
* docs: use the dynamic README header endpoint

* docs: add README header banners to the framework adapter packages
2026-08-03 21:03:29 +02:00
github-actions[bot]
ffaa0ba799
ci: Version Packages (beta) (#7933)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-08-01 21:13:10 +02:00
Brenley Dueck
3d40733d4a
Upgrade solidjs beta 29 + solid-query beta 7 (#7928)
* Upgrade solidjs beta 29

Upgrade `solid-js`, `@solidjs/web` and `babel-preset-solid` to
`2.0.0-beta.29`, and `vite-plugin-solid` to `3.0.0-next.20`
(peer-requires `>=2.0.0-beta.28`).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* Upgrade vite-plugin-solid to 3.0.0-next.21

Peer-requires `>=2.0.0-beta.29` (already satisfied) and ships
`@dom-expressions/compiler@0.50.0-next.34`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* Upgrade @tanstack/solid-query to 6.0.0-beta.7

Bump `@tanstack/solid-query` and `@tanstack/solid-query-devtools` to
`6.0.0-beta.7`. The devtools package peer-requires
`@tanstack/solid-query: ^6.0.0-beta.7`, so the two must move together.

`@tanstack/solid-query` is pinned through the `catalog:` entry in
pnpm-workspace.yaml and forced repo-wide via `overrides`, so the catalog
value is bumped alongside the package.json ranges — editing the
package.json ranges alone has no effect on resolution.

Both packages are added to `minimumReleaseAgeExclude`; the repo gates on
`minimumReleaseAge: 1440` and these betas are newer than that.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-08-01 20:57:52 +02:00
github-actions[bot]
1d589e6d14
ci: Version Packages (beta) (#7917)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-28 18:32:49 -05:00
Brenley Dueck
84c43e0595
Upgrade solidjs beta 27 (#7916)
Upgrade `solid-js`, `@solidjs/web` and `babel-preset-solid` to
`2.0.0-beta.27`, and `vite-plugin-solid` to `3.0.0-next.17`
(peer-requires `>=2.0.0-beta.26`).

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-07-29 00:45:44 +02:00
Tanner Linsley
179d9b9b5e
Improve Router and Start agent skills (#7867)
* docs: improve Router and Start agent skills

* docs: address agent skill review feedback

* ci: apply automated fixes

* docs: align agent skills with intent schema

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-26 10:53:49 -06:00
github-actions[bot]
254dfdea34
ci: Version Packages (beta) (#7890)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-25 15:36:40 +02:00
Brenley Dueck
a7e9835e1c
Upgrade solidjs beta 25 (#7888)
* Upgrade solidjs beta 25

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Upgrade vite-plugin-solid to 3.0.0-next.16

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-23 23:17:19 +02:00
Manuel Schiller
88f366ab8e
chore: migrate to typescript 7 (#7887) 2026-07-23 23:10:51 +02:00
Flo
3a5575627d
test: add regression coverage for existing router behavior (#7886) 2026-07-23 22:13:21 +02:00
github-actions[bot]
f370e36b67
ci: Version Packages (beta) (#7866)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-21 16:33:32 +02:00
Brenley Dueck
714e11f191
Upgrade solidjs beta 21 (#7865) 2026-07-20 20:58:08 -05:00
github-actions[bot]
90652ce8dd
ci: Version Packages (beta) (#7851)
* ci: changeset release (beta)

* ci: changeset release (beta) [Self-Healing CI Rerun]

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
2026-07-18 14:26:15 -05:00
Brenley Dueck
62f3b2697f
Upgrade solidjs beta 20 (#7850)
* chore: upgrade Solid v2 packages to 2.0.0-beta.20

Bumps solid-js and @solidjs/web from 2.0.0-beta.19 to 2.0.0-beta.20 and
vite-plugin-solid from 3.0.0-next.11 to 3.0.0-next.13 across packages,
examples, e2e apps, and benchmarks.

vite-plugin-solid 3.0.0-next.13 defaults to the new native JSX backend
(@dom-expressions/compiler), which is an incomplete milestone build that
cannot compile components with element children yet ("Only text and
expression component children are implemented in the AST-native
milestone"). Every vite-plugin-solid call site now passes
compiler: 'babel' to keep the babel-preset-solid pipeline until the
native compiler matures.

Also fixes two pins that had gone stale: the quickstart-webpack example's
direct babel-preset-solid pin (stuck on beta.18) and
@rsbuild/plugin-solid's babel-preset-solid lockfile resolution (also
beta.18), so the compiler and runtime are in lockstep everywhere.

Verified with solid-router test:unit (client + server modes) and
e2e/solid-start/basic (pnpm build + test:e2e:local).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: use the native JSX compiler (vite-plugin-solid default)

Removes the compiler: 'babel' escape hatch from all vite-plugin-solid
call sites, returning to next.13's default native backend
(@dom-expressions/compiler).

The native compiler's only unimplemented construct that this repo used
was a fragment passed as a component's child (dom mode only). The single
instance — the redundant <>{props.children}</> wrapper in solid-router's
ClientOnly — is removed; props.children is a valid JSX child on its own.

Verified: solid-router test:unit (client + server), e2e/solid-start/basic
(pnpm build + test:e2e:local), and a direct scan of all 1353 solid
.tsx/.jsx files in the repo through @dom-expressions/compiler in both
dom and ssr modes with zero failures.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 18:10:06 +02:00
github-actions[bot]
7a0cf36164
ci: Version Packages (beta) (#7835)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-16 17:01:11 +02:00
Brenley Dueck
ebe104c01c
Upgrade solidjs beta 19 (#7813)
* chore: upgrade Solid v2 packages to 2.0.0-beta.16

Bumps solid-js, @solidjs/web, and babel-preset-solid from 2.0.0-beta.15
to 2.0.0-beta.16 across packages, examples, e2e apps, benchmarks, and
the pnpm overrides in pnpm-workspace.yaml.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade Solid v2 packages to 2.0.0-beta.17

Bumps solid-js, @solidjs/web, and babel-preset-solid from 2.0.0-beta.16
to 2.0.0-beta.17 across packages, examples, e2e apps, and benchmarks.

The scoped babel-preset-solid overrides in pnpm-workspace.yaml are
removed instead of bumped: vite-plugin-solid@3.0.0-next.5 and
@rsbuild/plugin-solid@2.0.0-beta.0 both declare
'>=2.0.0-beta.0 <2.0.0-experimental.0', which resolves to the newest
v2 beta on its own, while Solid 1.x consumers keep babel-preset-solid
1.x. A stale override here silently kept the beta.16 compiler (with
its broken omitLastClosingTag marker handling) in the build pipeline.

The @dom-expressions/* scope is added to minimumReleaseAgeExclude,
covering the renamed compiler package (@dom-expressions/babel-plugin-jsx,
formerly babel-plugin-jsx-dom-expressions).

Two unrelated loose specs are pinned to their locked versions because
re-resolving the lockfile pulled broken releases: @platformatic/flame
1.7.0 fails pnpm's trust-downgrade policy, and the nitro-nightly
'latest' tag depends on an unpublished h3 version.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(solid-router): suspend on the match loadPromise only during SSR

On the client, returning the loadPromise from MatchInner's pending
branch keeps a live async source in the tree whenever a match is
pending. Since Solid 2.0.0-beta.16, that routes every signal write
into a transition hold for the rest of the flush, which breaks
router-core's synchronous write-then-load flows: invalidate() on a
notFound match never re-ran the loader, and writes to unrelated
signals were held too.

SSR keeps the suspension so the streaming engine waits for the match
to settle; the client now renders just the pending component.

Verified on beta.17: without this, "re-runs loaders that throw
notFound() when invalidated via HMR filter" and "keeps rendering a
route notFoundComponent when loader returns notFound() after
invalidate" fail.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(lockfile): restore all @rspack/binding@2.0.8 platform binaries

The lockfile entry for @rspack/binding@2.0.8 only listed the
darwin-arm64 binding, so linux CI runners had no matching native
binding and rspack fell back to a hoisted 2.0.0 binary, crashing the
bundle-size benchmark with a core/binding version mismatch.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: add changesets for solid-js beta.17 upgrade and SSR-only match suspension

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(examples): replace broken nitro-nightly pin with nitro beta in start-rscs

The pinned nitro-nightly@4.0.0-20251010 self-imports 'nitro/runtime/meta',
which under pnpm's isolated layout resolves to the hoisted nitro 3.x beta
and crashes vite config loading. Mirrors upstream fix e65f0c84c1 (#7809).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade vite-plugin-solid to next.7

* fix(solid-router): retain manifest stylesheets across navigation

* chore: upgrade Solid v2 packages to 2.0.0-beta.18 and vite-plugin-solid to next.8

Bumps solid-js, @solidjs/web, and babel-preset-solid from 2.0.0-beta.17
to 2.0.0-beta.18 and vite-plugin-solid from 3.0.0-next.7 to 3.0.0-next.8
(which pins @dom-expressions/jsx-compiler to 0.50.0-next.21) across
packages, examples, e2e apps, and benchmarks.

vite-plugin-solid is added to minimumReleaseAgeExclude: Solid publishes
plugin prereleases in lockstep with the runtime betas, often minutes
before we bump, and pnpm's 24h release-age gate otherwise filters the
new version with a misleading NO_MATCHING_VERSION error.

Verified: solid-router unit tests (client + server modes), solid-start
basic e2e (80 passed), solid-router basic-file-based e2e (120 passed),
and all 17 bundle-size benchmark scenarios build cleanly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(start-plugin-core): select client entry chunk by facade module instead of asserting a single entry

vite-plugin-solid >= 3.0.0-next.6 emits a facade chunk for every
dynamically imported project module during SSR client builds (to keep
its own manifest lookups stable), and emitted chunks are flagged
`isEntry` just like the configured entry. The start manifest capture
plugin asserted the client bundle contains exactly one entry chunk, so
every solid-start app failed to build with "multiple entries detected".

The capture plugin now receives the resolved client entry path and picks
the entry chunk whose facadeModuleId matches it; other entry-flagged
chunks are treated as ordinary chunks. When no chunk matches, a single
entry is still accepted as before, and the multiple-entries error now
lists every entry chunk with its facade module to ease diagnosis.

Verified with fresh package builds: previously failing memory-server
solid benchmark targets, all 17 bundle-size scenarios, solid-start basic
build + e2e (80 passed), react-start basic build, and the
start-plugin-core unit suite (494 tests).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci: apply automated fixes

* test(start-plugin-core): pass getClientEntry to startManifestPlugin in dev manifest test

Fixes the type tests after startManifestPlugin gained a required
getClientEntry option.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Revert "fix(start-plugin-core): select client entry chunk by facade module instead of asserting a single entry"

This reverts commit d0f4926ec0.

* chore: upgrade vite-plugin-solid to 3.0.0-next.10

next.10 ships the fix for the lazy facade entry reclassification under
rolldown-vite (solidjs/vite-plugin-solid#269): assigning isEntry = false
instead of deleting the property, so the reclassification actually
propagates through rolldown's bundle proxies and downstream plugins no
longer see every lazy facade chunk as an application entry. This is the
proper replacement for the reverted start-plugin-core workaround
(see a1ee1638f5) — the strict single-entry assertion now holds again.

Verified: e2e/solid-start/basic build + e2e suite (80 passed),
solid-router test:unit client (814) + server (2) modes,
start-plugin-core unit tests (486).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade solid-js/@solidjs/web to 2.0.0-beta.19 and vite-plugin-solid to 3.0.0-next.11

vite-plugin-solid 3.0.0-next.11 peer-requires solid-js and @solidjs/web
>=2.0.0-beta.19, so the Solid v2 packages are bumped in lockstep across
all workspace pins (packages, examples, e2e, benchmarks).

Verified: e2e/solid-start/basic build succeeds — no "multiple entries
detected" error from start-manifest-capture-client-build; solid-router
test:unit client (814 passed) + server (2 passed) modes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade solid-js/@solidjs/web to 2.0.0-beta.19 and vite-plugin-solid to 3.0.0-next.11 [Self-Healing CI Rerun]

* chore: upgrade solid-js/@solidjs/web to 2.0.0-beta.19 and vite-plugin-solid to 3.0.0-next.11 [Self-Healing CI Rerun]

* fix(e2e): make prerender builds hermetic to deflake build:vite:prerender

The prerender crawl runs inside `vite build` and SSRs /posts and every
crawled /posts/$postId. The `import.meta.env.VITE_NODE_ENV === 'test'`
switch to the local dummy server was inlined away at build time because
Playwright only sets that env for the test-time webServer, never for the
nx build target — so build-time SSR fetched the real
jsonplaceholder.typicode.com from CI. When that public API stalled, the
page never sent headers and the build died after undici's 5-minute
headers timeout (UND_ERR_HEADERS_TIMEOUT).

Fix, applied to the react/solid/vue basic apps alike:
- Resolve the posts/users API base URL at request time from process.env
  (same pattern users.tsx already used) instead of build-time inlining,
  so the built app honors whatever dummy server the harness is running.
- Add e2eStartDummyServerForBuild() to @tanstack/router-e2e-utils and
  call it from the apps' vite configs in prerender mode: it starts the
  dummy server on a free port for the lifetime of the build, exposes it
  via VITE_NODE_ENV/VITE_EXTERNAL_PORT, and unrefs everything so the
  build process can exit.

Verified: nx run tanstack-solid-start-e2e-basic:build:vite:prerender
passes (47 pages prerendered, dummy server used, tsc clean), prerendered
posts/index.html contains the expected content, and the server bundle
now keeps the runtime env check instead of a hardcoded external URL.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci: apply automated fixes

* chore: upgrade solid-js/@solidjs/web to 2.0.0-beta.19 and vite-plugin-solid to 3.0.0-next.11 [Self-Healing CI Rerun]

* fix(e2e): harden prerender-build dummy server and log fetch targets

CI still hit UND_ERR_HEADERS_TIMEOUT during build:vite:prerender after
de2132af1b. The failure pattern (fetch logs print instantly, then a
5-minute stall) means the posts fetches still reached the real external
API in that run: the dummy server resolves in milliseconds in-process,
and a non-listening port would fail instantly with ECONNREFUSED.

One way that can happen: e2eStartDummyServerForBuild() early-returned
whenever VITE_EXTERNAL_PORT was already present in the environment,
skipping both the server start AND setting VITE_NODE_ENV — leaving the
runtime URL check pointing at jsonplaceholder. Guard on a globalThis
flag instead and always set both env vars.

Also, to make the next failure diagnosable and survivable:
- fetchPost/fetchPosts (react/solid/vue basic) now log the base URL they
  fetch from, so CI output shows whether the dummy server was used.
- prerender configs set retryCount: 2 / retryDelay: 1000 so a transient
  hang retries instead of failing the whole build.

Verified: nx run tanstack-solid-start-e2e-basic:build:vite:prerender
passes with "Fetching posts from http://localhost:<port>..." in the log
and 47 pages prerendered.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
2026-07-16 16:17:49 +02:00
github-actions[bot]
58c005fcb1
ci: Version Packages (#7811) 2026-07-13 23:31:08 +02:00
github-actions[bot]
0e4f15d741
ci: Version Packages (beta) (#7736) 2026-07-03 02:44:44 +02:00
Brenley Dueck
f9b0e57ce0
fix(solid-router): resolve defaultNotFoundComponent at render time to avoid hydration desync (#7734)
* fix(solid-router): resolve defaultNotFoundComponent at render time to avoid hydration desync

Previously defaultNotFoundComponent was applied by lazily mutating the
boundary route's options.notFoundComponent when a notFound was handled.
Route objects are module singletons shared across server requests, so
once the server handled any 404, later SSRs of valid URLs wrapped the
match in a CatchNotFound boundary the freshly-hydrating client doesn't
render, shifting hydration keys and leaving the subtree unclaimed
(visible but inert DOM).

Resolve defaultNotFoundComponent at render time in Match.tsx so the
boundary structure is deterministic on both server and client, and add
an e2e regression test.

* ci: apply automated fixes

* chore: add changeset for defaultNotFoundComponent hydration fix

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-03 01:47:05 +02:00
github-actions[bot]
ecbbd9a8ec
ci: Version Packages (#7676)
ci: changeset release

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-01 23:33:19 +02:00
github-actions[bot]
3d265ea439
ci: Version Packages (beta) (#7649)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-06-25 03:00:11 +02:00
Brenley Dueck
259efbe530
chore: upgrade solid-js to 2.0.0-beta.15 (#7688)
Bump solid-js and @solidjs/web from 2.0.0-beta.14 to 2.0.0-beta.15
across all packages, examples, and e2e apps.

- Pin solid-js as an explicit devDependency in @tanstack/solid-router
  (it previously only declared a floating peer range, so pnpm kept it
  on beta.14).
- Update the scoped vite-plugin-solid babel-preset-solid override to
  beta.15 and add a matching scoped override for @rsbuild/plugin-solid.
- Add minimumReleaseAgeExclude for the freshly published solid betas.
- router-devtools-core intentionally stays on Solid v1.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-25 02:42:21 +02:00
Brenley Dueck
51b4bd4f37
perf(solid-router): proxy-free link props in the spread hot path (#7609)
useLinkProps stacked four proxies (merge of defaults, two omit proxies,
and a final merge with the resolved-props memo), and Solid's spread()
re-enumerated them through V8 proxy traps on every navigation for every
Link. Return a plain object with a stable key set instead, with
reactivity in property getters backed by fine-grained memos, and add
href-based equality to the built-location memo.

Client-side navigation benchmark: 7.06ms -> 4.80ms per iteration.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-06-18 03:45:48 +02:00
github-actions[bot]
f23ed0fe73
ci: Version Packages (#7576) 2026-06-17 00:12:54 +02:00
autofix-ci[bot]
0747d9b8fa
ci: apply automated fixes 2026-06-13 21:09:57 +00:00
Brenley Dueck
545866dd47 chore: fix tests 2026-06-13 16:07:04 -05:00
Brenley Dueck
1052ab97ba Merge branch 'main' into solid-router-main-merge2 2026-06-13 15:54:31 -05:00
Flo
41e7a24f69
refactor(solid-router): remove unnecessary setTimeout from Match components (#7584) 2026-06-07 23:05:20 +02:00
github-actions[bot]
10a7ff833c
ci: Version Packages (#7563) 2026-06-06 11:49:34 +02:00
github-actions[bot]
996b9bee38
ci: Version Packages (#7561) 2026-06-06 10:45:35 +02:00
github-actions[bot]
65ad9062ea
ci: Version Packages (#7556) 2026-06-06 01:01:21 +02:00
github-actions[bot]
a8647d20a1
ci: Version Packages (#7554) 2026-06-05 22:11:34 +02:00
Ulrich Stark
fee0b58c51
refactor: remove unused dependencies (#7541) 2026-06-04 22:47:41 +02:00
Ulrich Stark
bb99f66a47
refactor: remove unnecessary any assertions (#7542) 2026-06-04 22:12:45 +02:00
github-actions[bot]
65133ed03f
ci: Version Packages (beta) (#7539)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-06-04 00:18:19 +02:00
Birk Skyum
ff136aaea6
fix(solid-router-v2): use TSR_DEFERRED_PROMISE (#7532) 2026-06-03 23:28:58 +02:00
github-actions[bot]
fc8ad80851
ci: Version Packages (beta) (#7528)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-06-02 23:05:48 +02:00
Birk Skyum
0ce852a287
Revert "ci: Version Packages (beta) (#7526)"
This reverts commit 09c50944a9.
2026-06-02 22:54:47 +02:00
github-actions[bot]
09c50944a9
ci: Version Packages (beta) (#7526)
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-06-02 22:50:23 +02:00
github-actions[bot]
7fc7c346dc
ci: Version Packages (#7525)
ci: changeset release

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-06-02 22:50:10 +02:00
autofix-ci[bot]
fe28cbc285
ci: apply automated fixes 2026-06-01 23:46:05 +00:00