Overview - Router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
7813
8b7516c7 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>
by Brenley Dueck
Failed
7813
Flaky task→
b0826975 ci: apply automated fixes
by autofix-ci...
Failed
7813
Flaky task→
ab35ca52 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]
by nx-cloud[bot]
Canceled
7813
ab35ca52 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]
by nx-cloud[bot]
Failed
7813
Flaky task→
ab35ca52 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]
by nx-cloud[bot]
Failed
7813
Flaky task→
6a5534c0 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>
by Brenley Dueck
Failed
7813
Flaky task→
6a5534c0 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>
by Brenley Dueck
Failed
7813
Fix ready→
d81a2445 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>
by Brenley Dueck
Failed
7813
a1ee1638 Revert "fix(start-plugin-core): select client entry chunk by facade module instead of asserting a single entry" This reverts commit d0f4926ec0739ef4ba1e92dbbba68061a57bb528.
by Brenley Dueck
Succeeded
7813
f1f590ce ci: apply automated fixes
by autofix-ci...
Failed
7813
Fix ready→
f7805a8c 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>
by Brenley Dueck
Succeeded
7813
f7805a8c 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>
by Brenley Dueck
Canceled
7813
f7805a8c 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>
by Brenley Dueck
Failed
7813
f7805a8c 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>
by Brenley Dueck
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