@rsc-kit/mcp 0.20.11 → 0.20.12

package/guides/getting-started.md

@@ -58,7 +58,7 @@ generation](/guides/static-generation).
 With the Bun preset the whole application ends up in one file:
 
 ```bash
-npm run compile   # builds, then bun build --compile
+npm run compile   # builds, then bun build --compile --keep-names
 ./dist/app
 ```
 

package/guides/installation.md

@@ -170,7 +170,7 @@ runs](/hosts/where-it-runs).
     "dev": "bun --bun vite",
     "build": "bun --bun vite build",
     "start": "bun .output/server/index.mjs",
-    "compile": "bun --bun vite build && bun build --compile .output/server/compile.mjs --outfile dist/app"
+    "compile": "bun --bun vite build && bun build --compile --keep-names .output/server/compile.mjs --outfile dist/app"
   }
 }
 ```

package/guides/ppr.md

@@ -51,6 +51,25 @@ the page's title and description into the head when it serves the shell for
 a url it does know; the client sets the title again after hydration. Static
 `metadata` on the page and the layouts is in the shell as always.
 
+## A shell and the server that finishes it are one build
+
+A postponed state names the components React has to find when it replays, and
+a name is whatever that build's minifier assigned. Resumed against a different
+bundle, the same component answers to something else:
+
+```text
+Expected the resume to render <J> in this slot but instead it rendered <J2>.
+```
+
+Two names for one component is the fingerprint of two builds. Every shell is
+stamped with the build that froze it, and a host that finds a shell from
+another build serves it but renders the page whole instead of resuming it,
+with a line in the log saying so.
+
+How they drift apart in practice: a Docker layer, a CI cache or a volume that
+keeps a previous prerender output while the server bundle is rebuilt. Build
+both together, or clear the output directory between builds.
+
 ## A shell for a pattern is one shape
 
 A route with params that listed no urls is frozen **once**, for the pattern —

package/guides/where-it-runs.md

@@ -65,7 +65,7 @@ Bun only, and the whole application ends up inside one file — engine, route
 tree, frozen pages and assets, the precompressed variants included:
 
 ```bash
-npm run compile   # builds, then bun build --compile .output/server/compile.mjs
+npm run compile   # builds, then bun build --compile --keep-names .output/server/compile.mjs
 ./dist/app
 ```
 
@@ -82,7 +82,22 @@ a binary one version behind the source with nothing to say so — and on a
 project that has never been built, an `ENOENT` naming a path the app did not
 write.
 
-`--compile` implies `--production`; `--target bun` is the default. `--bytecode`
+**`--keep-names` is not optional.** `--compile` implies `--production`, which
+minifies — and minifying renames every function. A partially prerendered page
+is finished by replaying a tree the build recorded by component *name*, so a
+binary that renamed them finds the wrong name in every slot:
+
+```text
+Expected the resume to render <J> in this slot but instead it rendered <J2>.
+```
+
+React then falls back to client rendering for every hole, and the page arrives
+looking finished with nothing wired up. `--keep-names` preserves the names the
+build recorded, and costs a few kilobytes. A build with no PPR route never
+notices; one with them fails only on a cold load, in production, which is the
+worst way to find out.
+
+`--target bun` is the default. `--bytecode`
 compiles the JavaScript ahead of time for a faster cold start at the cost
 of a larger binary — a production port measured 275 ms → 72 ms to the first
 healthy response for 81 MB → 117 MB, and left it out, since on a pod the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rsc-kit/mcp",
-  "version": "0.20.11",
+  "version": "0.20.12",
   "description": "An MCP server over what an rsc-kit build decided: the routes, why each one is static or not, and what it costs the browser.",
   "type": "module",
   "license": "MIT",