From 5555334eeb511d3698de04a4940f2999b7a3a673 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 20 Oct 2026 22:30:16 +0000 Subject: [PATCH] Version Packages --- .changeset/static-wire-answers.md | 16 ---------------- packages/crawler/CHANGELOG.md | 16 ++++++++++++++++ packages/crawler/package.json | 2 +- packages/solid/CHANGELOG.md | 16 ++++++++++++++++ packages/solid/package.json | 2 +- 5 files changed, 34 insertions(+), 18 deletions(-) delete mode 100644 .changeset/static-wire-answers.md diff --git a/.changeset/static-wire-answers.md b/.changeset/static-wire-answers.md deleted file mode 100644 index 0482afe..0000000 --- a/.changeset/static-wire-answers.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -"@solidjs/prerender": minor -"prerender-crawler": minor ---- - -Prerendered calls now store the live answer, so server components can be prerendered. - -**`@solidjs/prerender`.** An artifact is now the response the app's own server-function endpoint gives for the call's GET address (status, headers and body), captured by replaying each call through the crawl after the pages render. Before, the integration encoded the returned value itself, which bypassed the server's result policies: a server component (`return props => `) was stored as an error, and client navigation to it crashed in both static and hybrid builds. - -On the client, `prerendered()` now returns the runtime's own GET reference and serves artifacts through the reference's own send (`withMeta(fn, { fetch })`), so an app's transport `fetch` stays the app's and carries the hybrid fallback. Hydration adopts server-rendered reads and server components without a request, where it used to refetch them, and responses decode through the runtime's own pipeline. Artifacts are recognized by a marker line instead of status, so a host answering a missing artifact with a 200 page now falls back to the live server in hybrid mode instead of failing to parse. - -Artifacts live under the build's id (`_static//…`), so they can be cached as immutable and a deploy never serves the previous build's answer from a CDN. - -Breaking: artifacts are `_static//