Update dependency @solidjs/start to v2.0.0-rc.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@solidjs/start (source)	2.0.0-rc.1 → 2.0.0-rc.6

---

Release Notes

solidjs/solid-start (@​solidjs/start)

v2.0.0-rc.6

Compare Source

Minor Changes

• bac24b2: Add a serverFunctions.onError option naming a module that observes and replaces what a server function threw, before it is serialized into the response

Patch Changes

• 27c2877: Remove leftover debug console.log calls from the server functions inspector, which logged on every server function request in dev.
• f15724b: Declare @solidjs/router as an optional peer dependency constrained to >=0.16.0 <2.0.0-0. Router v2 is expected to target Solid v2, so installing it alongside @solidjs/start v2 now surfaces a peer warning instead of silently producing an incompatible pairing. The peer is marked optional, so apps that do not use the router are unaffected.
• 5c8612f: Apply cookies set on a returned or thrown response during single flight mutations. redirect(to, { headers: { "Set-Cookie": ... } }) previously only reached the browser: the single flight re-render of the redirect target still ran with the old request cookies, so queries reading that cookie saw stale values. Those cookies are now merged into the request the re-render sees, matching what a browser round trip would have sent.
• 83122ed: Reject server function calls when the response is a 5xx without an X-Error header, instead of resolving with the parsed error body

v2.0.0-rc.5

Compare Source

Minor Changes

• 4c803e5: Add serialization.plugins to configure custom Seroval plugins for server functions.

  Values Seroval has no built-in support for (Mongo's ObjectId, Prisma's Decimal, Temporal, and other custom classes) previously threw when returned from or passed to a server function. Point the new option at a module whose default export is an array of plugins:

  // vite.config.ts
  solidStart({
    serialization: {
      plugins: "src/seroval-plugins.ts",
    },
  });

  // src/seroval-plugins.ts
  import { createPlugin } from "@​solidjs/start/serialization";

  The module is bundled into both the client and the server so both ends of a server function agree on the format, so it must not import server-only code. SolidStart's built-in plugins keep precedence. Only server-function and action payloads are affected; the SSR hydration payload is serialized by solid-js/web.

  Also adds a @solidjs/start/serialization entrypoint re-exporting Seroval's createPlugin, OpaqueReference, and plugin types, so plugin authors stay on the same Seroval version SolidStart serializes with.

Patch Changes

• e117d91: Route module ids now end in the source extension, so ecosystem plugins apply inside src/routes.

  Route files are imported through an id carrying the picked exports in the query (routes/api.ts?pick=GET), which left the id ending in the export name. Plugins whose filter is anchored on the file extension (/\.[cm]?[jt]sx?$/, the default for unplugin-auto-import, unplugin-macros and others) silently skipped every route file. The id now ends with a lang.<ext> marker, the same convention Vue SFCs use for ?vue&type=script&lang.ts. Chunk filenames are unchanged.

• d8f1ea8: Apply the configured nonce to the two script tags that were still missing it, so a strict script-src CSP no longer needs unsafe-inline:

  • The client-side redirect that streaming mode emits after the shell has already flushed (<script>window.location=...</script>) now carries the nonce.
  • The SPA entry script tag now carries the nonce, matching the SSR entry script.

• 27fca88: Fix actions returning json() or reload() leaving no-JS form submissions stranded on the /_server endpoint. These responses carry a value rather than a destination, so the redirect issued for progressive-enhancement submissions had no Location header. It now falls back to the submitting page, and the response value is unwrapped into the flash cookie so useSubmission().result matches the JS path.

• 75debc3: Scope the built-in ~ alias to the app package, so files in other workspace packages can map ~ to their own root through an importer-aware plugin such as vite-tsconfig-paths. In stylesheets and asset URLs (CSS @import, url(), new URL(..., import.meta.url)) ~ still always means the app root, since Vite resolves those without running plugins.

v2.0.0-rc.4

Compare Source

Patch Changes

• b6dfaac: Updated dependencies, including cookie-es to 3, shiki to 4, srvx to 0.12.4, oxc-parser to 0.141 and seroval to 1.5.6. parseSetCookie now returns undefined for cookies with a forbidden name or an empty name and value, and those cookies are no longer forwarded to nested server function requests.
• 02cd41e: Stop the dev toolbar from reporting benign ResizeObserver loop notifications as application errors. Browsers dispatch these as window error events carrying no error object, so the toolbar was capturing the raw ErrorEvent and force-opening the error panel over the app on every resize.
• d3c2af2: Don't send server error stack traces to the client in production builds. When a server function throws, the error is serialized and rethrown on the client, and seroval included Error.prototype.stack by default, leaking server file paths and internal function names. Stacks are still serialized in development.

v2.0.0-rc.3

Compare Source

Patch Changes

• d9018d6: fix(types): add missing properties to SolidStartOptions and expose them via Vite plugin configuration
• e26cef0: Fix TS2883/TS2742 when emitting declarations for entry-server.tsx. createHandler now returns StartHandler, a type owned by @solidjs/start, instead of h3's H3, so the inferred type of export default createHandler(...) no longer has to be named through a nested node_modules/@​solidjs/start/node_modules/h3 path.
• 7c8dbe6: keep TypeScript namespace members in route files during production builds
• b3c7aaf: Update h3 to 2.0.1-rc.26.
• b3c7aaf: Fixed event response status and headers set during server-side rendering with deferred async resources, not being applied on the outgoing response.

v2.0.0-rc.2

Compare Source

Minor Changes

• eeff49a: add new dev toolbar

Patch Changes

• bd8cb01: Update srvx to version 0.12.0.
• 4e98ac0: Restore the optional routerLoad third argument to createHandler, which primes custom routers (e.g. TanStack Router) on the server before SSR rendering. It was accidentally dropped in the v2 rewrite.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 2 workspace projects
? Verifying lockfile against supply-chain policies (679 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 21, reused 0, downloaded 0, added 0
Progress: resolved 26, reused 0, downloaded 0, added 0
Progress: resolved 27, reused 0, downloaded 0, added 0
Progress: resolved 28, reused 0, downloaded 0, added 0

   ╭──────────────────────────────────────────╮
   │                                          │
   │   Update available! 11.9.0 → 11.17.0.    │
   │   Changelog: https://pnpm.io/v/11.17.0   │
   │     To update, run: pnpm add -g pnpm     │
   │                                          │
   ╰──────────────────────────────────────────╯

Progress: resolved 29, reused 0, downloaded 0, added 0
Progress: resolved 31, reused 0, downloaded 0, added 0
Progress: resolved 32, reused 0, downloaded 0, added 0
Progress: resolved 33, reused 0, downloaded 0, added 0
Progress: resolved 36, reused 0, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (679 entries in 12.3s)
Progress: resolved 38, reused 0, downloaded 0, added 0
Progress: resolved 179, reused 0, downloaded 0, added 0
Progress: resolved 198, reused 0, downloaded 0, added 0
Progress: resolved 202, reused 0, downloaded 0, added 0
Progress: resolved 204, reused 0, downloaded 0, added 0
Progress: resolved 206, reused 0, downloaded 0, added 0
Progress: resolved 210, reused 0, downloaded 0, added 0
Progress: resolved 300, reused 0, downloaded 0, added 0
Progress: resolved 440, reused 0, downloaded 0, added 0
Progress: resolved 454, reused 0, downloaded 0, added 0
Progress: resolved 461, reused 0, downloaded 0, added 0
Progress: resolved 592, reused 0, downloaded 0, added 0
Progress: resolved 652, reused 0, downloaded 0, added 0
[ERR_PNPM_NO_MATURE_MATCHING_VERSION] 5 versions do not meet the minimumReleaseAge constraint:
  h3@2.0.1-rc.26 was published at 2026-07-24T18:49:24.063Z, within the minimumReleaseAge cutoff (2026-07-22T01:13:36.620Z)
  srvx@0.12.4 was published at 2026-07-22T16:56:45.608Z, within the minimumReleaseAge cutoff (2026-07-22T01:13:36.620Z)
  srvx@0.12.4 was published at 2026-07-22T16:56:45.608Z, within the minimumReleaseAge cutoff (2026-07-22T01:13:36.620Z)
  srvx@0.12.4 was published at 2026-07-22T16:56:45.608Z, within the minimumReleaseAge cutoff (2026-07-22T01:13:36.620Z)
  srvx@0.12.4 was published at 2026-07-22T16:56:45.608Z, within the minimumReleaseAge cutoff (2026-07-22T01:13:36.620Z)

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[netlify]

❌ Deploy Preview for solid-docs failed. Why did it fail? →

Name	Link
🔨 Latest commit	fb91b3a
🔍 Latest deploy log	https://app.netlify.com/projects/solid-docs/deploys/6a6953f3a07fe3000739887b

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.