create-rsc-kit 0.8.0 → 0.9.0

package/dist/templates.js

@@ -196,7 +196,11 @@ export function viteConfig(o) {
     //
     // Not optional, and not a flag on rscKit() either — the plugin builds for
     // Nitro and nothing else, so a config without this line has no server.
-    plugins.push(`nitro({ preset: ${JSON.stringify(preset(o.host))}, serveStatic: 'inline' })`);
+    // serverDir is what makes server/api and server/routes exist at all: Nitro's
+    // scanDirs is empty without it, so a handler written there is never scanned,
+    // the request falls through to the rsc entry, and the 404 it answers with
+    // reads as a routing bug in this package rather than a missing option.
+    plugins.push(`nitro({ preset: ${JSON.stringify(preset(o.host))}, serveStatic: 'inline', serverDir: 'server' })`);
     plugins.push(`rscKit({
       ${options.join(',\n      ')},
     })`);
@@ -205,12 +209,22 @@ export function viteConfig(o) {
         plugins.push('babel({ presets: [reactCompilerPreset()] })');
     if (o.tailwind)
         plugins.push('tailwindcss()');
+    // `@/` for the source directory. Vite does not read tsconfig `paths`, so the
+    // alias has to exist here as well or the import type-checks and then fails to
+    // resolve — and the tsconfig half is what tools like shadcn look for when
+    // they ask whether this project has an import alias at all.
     return `${imports.join('\n')}
+import { fileURLToPath } from 'node:url'
 
 export default defineConfig({
   plugins: [
     ${plugins.join(',\n    ')},
   ],
+  resolve: {
+    alias: {
+      '@': fileURLToPath(new URL('./${o.sourceDir}', import.meta.url)),
+    },
+  },
 })
 `;
 }
@@ -220,6 +234,16 @@ export const tsconfig = (o) => JSON.stringify({
         target: 'ESNext',
         module: 'ESNext',
         moduleResolution: 'bundler',
+        // `@/thing` for `<sourceDir>/thing`. Matched by resolve.alias in the
+        // vite config, which is what actually resolves it — this half is for
+        // the type system, and for the tools that read a tsconfig to find out
+        // whether the project has an import alias. shadcn refuses to init
+        // without one.
+        //
+        // No `baseUrl`: TypeScript removed it, and emitting it now is an
+        // outright TS5102 on a freshly scaffolded app. Paths resolve relative
+        // to this file without it.
+        paths: { '@/*': [`./${o.sourceDir}/*`] },
         jsx: 'react-jsx',
         strict: true,
         noEmit: true,
@@ -249,12 +273,17 @@ export const tsconfig = (o) => JSON.stringify({
     // .rsc-kit holds the generated ambient declarations. Ambient means
     // inside the project, and `include` is what decides that — leave it out
     // and typed routes silently fall back to string.
-    include: [`${o.sourceDir}/**/*`, '.rsc-kit/**/*'],
+    //
+    // server/ is the same mistake one directory over: an api handler outside
+    // the program is not type-checked at all, so one returning the wrong
+    // shape builds, deploys and fails at runtime with nothing having said so.
+    include: [`${o.sourceDir}/**/*`, 'server/**/*', '.rsc-kit/**/*'],
 }, null, 2) + '\n';
 export function layout(o) {
     return `${o.tailwind ? "import './styles.css'\n" : ''}import type { ReactNode } from 'react'
+import type { Metadata } from '@rsc-kit/core/metadata'
 
-export const metadata = {
+export const metadata: Metadata = {
   title: { template: '%s · ${o.name}', default: '${o.name}' },
 }
 
@@ -288,8 +317,9 @@ export function page(o) {
     // did was look broken, and the fix someone reaches for is to stop
     // prerendering the page that is teaching them about prerendering.
     return `import { Counter } from '../components/Counter'
+import type { Metadata } from '@rsc-kit/core/metadata'
 
-export const metadata = { title: 'Home' }
+export const metadata: Metadata = { title: 'Home' }
 
 // A server component. It runs on the server and ships no JavaScript of its
 // own — this file is not in the browser bundle. It can be \`async\` and await

package/package.json

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