Overview - Router

router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
7813
f657680f chore: upgrade vite-plugin-solid to next.7
by Brenley Dueck
Failed
7813
68cc84ba 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>
by Brenley Dueck
Failed
7813
9d02a637 chore: add changesets for solid-js beta.17 upgrade and SSR-only match suspension Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Brenley Dueck
Failed
7813
76f6d00a 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>
by Brenley Dueck
Failed
7813
Environment issue→
76f6d00a 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>
by Brenley Dueck