create-rsc-kit 0.16.0 → 0.16.2

package/README.md

@@ -20,4 +20,4 @@ payload to a production client, a stylesheet with no server-component classes
 in it, an engine declaration that typechecks the server and fails the prerender.
 What comes out has those right.
 
-Docs: https://rsc-kit.dev · Licence: MIT
+Docs: https://docs.rsc-kit.dev · Licence: MIT

package/dist/templates.js

@@ -126,7 +126,7 @@ export function packageJson(o) {
         // every route. TanStack Start pins a dated beta for the same reason.
         nitro: '3.0.260903-beta',
         ...(o.host === 'worker'
-            ? { wrangler: '^4.0.0', '@cloudflare/workers-types': '^4.0.0' }
+            ? { wrangler: '^4.0.0', '@cloudflare/workers-types': '^5.0.0' }
             : {}),
         // Not redundant, though it is also the engine's peer: the generated entry
         // imports '@vitejs/plugin-rsc/rsc' by specifier, so it has to resolve from
@@ -265,9 +265,10 @@ export const tsconfig = (o) => JSON.stringify({
         skipLibCheck: true,
         resolveJsonModule: true,
         types: o.host === 'worker'
-            ? // A Worker has neither node globals nor Bun's. Its own types, and
-                // vite/client for import.meta.env.
-                ['@cloudflare/workers-types', 'vite/client']
+            ? // A Worker has neither node globals nor Bun's: its own types, and
+                // vite/client for import.meta.env. Bun's as well, because the
+                // tests run under bun:test - the two sets coexist.
+                ['@cloudflare/workers-types', 'vite/client', '@types/bun']
             : o.host === 'node'
                 ? ['node', 'vite/client']
                 : ['@types/bun', 'vite/client'],
@@ -507,7 +508,7 @@ React Server Components through \`@rsc-kit/core\`, a Vite plugin. Routes are
 files under \`${o.sourceDir}/app\`. There is no server file to edit — the build
 generates it.
 
-Read the guides at https://rsc-kit.dev before reaching for a pattern from
+Read the guides at https://docs.rsc-kit.dev before reaching for a pattern from
 another framework. The notes below are only the things most often got wrong.
 
 The \`rsc-kit\` MCP server in \`.mcp.json\` answers from this project's last
@@ -718,8 +719,9 @@ deploys is changing that one string.${compile}
 
 Freezing is part of \`build\`: it renders every page it can and stores the
 result, so those pages are read off disk instead of rendered per visitor.
-Turn it off with \`rscKit({ prerender: false })\` when the build machine
-cannot do what the pages need.
+There is no switch to turn it off for the app; a page that must render per
+request says \`await connection()\`, and the build names any page it could
+not render.
 
 ## Where things go
 
@@ -735,6 +737,6 @@ A directory with a \`page.tsx\` is a route, so \`src/app/about/page.tsx\` is
 \`.rsc-kit/\` is the build's: the route types that make \`href\` checkable, and
 the ambient declarations. Rewritten every build, and gitignored.
 
-Docs: https://rsc-kit.dev
+Docs: https://docs.rsc-kit.dev
 `;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-rsc-kit",
-  "version": "0.16.0",
+  "version": "0.16.2",
   "type": "module",
   "description": "Scaffold an RSC app on Bun, Hono, Elysia or Node.",
   "bin": {