@rshono/create 1.0.0-rc.6 → 1.0.0-rc.7

package/README.md

@@ -26,49 +26,72 @@ arrived in pnpm 10.16, before which it is `pnpm dlx`.
 
 Six, each with a default, and each answerable by a flag instead:
 
-| Question              | Default            | Flag                                                                |
-| --------------------- | ------------------ | ------------------------------------------------------------------- |
-| Where should it go?   | `my-rshono-app`    | first positional argument, or `.`                                   |
-| Where is it deployed? | `node`             | `--deploy node\|bun\|deno\|cloudflare\|vercel\|netlify\|aws-lambda` |
-| Styling               | plain CSS          | `--tailwind` / `--no-tailwind`                                      |
-| Formatting & linting  | Prettier + oxlint  | `--quality prettier-oxlint\|prettier-eslint\|biome\|oxc\|none`      |
-| Install dependencies? | yes                | `--no-install`                                                      |
-| Initialize git?       | yes, unless nested | `--no-git`                                                          |
-
-Plus `--formatter` and `--linter` to set either half of the quality preset on its own, `--pm` to override
-the package manager that was detected, `--force` to scaffold into a directory that is not empty,
-`--dry-run` to see the file list and write nothing, and `-y` to take the defaults for everything not
-given. **A non-interactive terminal implies `-y`**, so this is one command in CI or from an agent:
+| Question              | Default            | Flag                                                           |
+| --------------------- | ------------------ | -------------------------------------------------------------- |
+| Where should it go?   | `my-rshono-app`    | first positional argument, or `.`                              |
+| Where is it deployed? | `node`             | `-d, --deploy node\|cloudflare\|vercel\|aws-lambda`            |
+| Styling               | plain CSS          | `--tailwind` / `--no-tailwind`                                 |
+| Formatting & linting  | Prettier + oxlint  | `--quality prettier-oxlint\|prettier-eslint\|biome\|oxc\|none` |
+| Install dependencies? | yes                | `--no-install`                                                 |
+| Initialize git?       | yes, unless nested | `--no-git`                                                     |
+
+Plus `--formatter prettier\|biome\|oxfmt\|none` and `--linter oxlint\|eslint\|biome\|none` to set either half
+of the quality preset on its own, `--pm npm\|pnpm\|yarn\|bun` to override the package manager that was
+detected, `--force` to scaffold into a directory that is not empty, `--dry-run` to see the file list and write
+nothing, and `-y` to take the defaults for everything not given. **A non-interactive terminal implies `-y`**,
+so this is one command in CI or from an agent:
 
 ```bash
 npx @rshono/create@latest my-app -y --deploy cloudflare --tailwind --quality biome
 ```
 
-The deploy targets, and the deploy command each one prints, are generated from the framework's own
-presets — a target added to rshono appears here with no edit.
+The deploy targets, and the deploy command each one prints, are generated from the framework's own presets —
+a target added to rshono appears here with no edit.
 
 ## What you get
 
 ```
+package.json            scripts, and the exact dependency versions rshono is tested against
 rshono.config.ts        the chosen deploy target; every other setting takes its default
 tsconfig.json           strict, with @/* → ./src/*
 .env                    committed defaults; secrets go in .env.local
+.gitignore              plus whatever each chosen feature adds, under a heading naming it
+README.md               the app's own commands, layout and deploy step
 public/                 favicon.svg, robots.txt
 src/routes.ts           one page, a 404 and a 500
 src/server.ts           error reporting, trailing-slash and old-path redirects, AppType
 src/components/         layout, home, 404, 500
 src/styles.css          element-level CSS, or the Tailwind entry
+src/env.d.ts            the CSS-import declaration the compiler needs
 pnpm-workspace.yaml     pnpm only: which dependency install scripts this app runs (none of them)
 ```
 
-Scaffolding runs the install and nothing else — no formatter, no linter. The templates are written to
-satisfy every formatter option at its configured width, so a fresh project passes its own `format:check`
-without a write pass first.
+Scaffolding runs the install and nothing else — no formatter, no linter. The templates are written to satisfy
+every formatter option at its configured width, so a fresh project passes its own `format:check` without a
+write pass first.
 
 `react` and `react-dom` are pinned **exactly**, at the versions the framework is tested against, and those
 pins are generated from rshono's own manifest. That is not tidiness: the RSC runtime reaches into React's
 internals, and an app installed with npm or bun has no workspace overrides to keep a single copy of it.
 
+## Two things worth knowing
+
+**The ESLint preset pins TypeScript 6.** Linting TypeScript with ESLint means `typescript-eslint`, which reads
+the compiler API directly rather than through a stable interface, so its peer range is
+`typescript >=4.8.4 <6.1.0` — below the TypeScript rshono is built and tested against. An app that chooses
+ESLint therefore gets `typescript ~6.0.3`, the newest that range allows: `npm install` would otherwise fail
+outright on the conflict, and forcing past it hands you a linter running against a compiler API it was never
+built for. The framework's declarations compile identically under either version, which is what makes this the
+app's pin and not the framework's — every other preset leaves TypeScript alone. What you trade for type-aware
+rules is a compiler one major behind, and the JavaScript implementation rather than the native one, so
+`typecheck` on a large app is several times slower. When upstream widens the range, the pin in
+`features/quality.ts` is the only thing to delete.
+
+**Tailwind is four packages, a `postcss.config.mjs` and one rule in `rshono.config.ts`.** rshono compiles CSS
+natively and has no PostCSS in it — that is deliberate, and it means an app that wants a plugin chain brings
+its own, through the `rspack` hook. The overlay writes all of it, with a comment saying what to delete to go
+back to plain CSS.
+
 ## Adding an option
 
 Every difference between two scaffolds is a `Feature` — files to overlay, dependencies, scripts,
@@ -77,37 +100,19 @@ edits and no new machinery:
 
 1. A `Feature` in `src/features/` — `templates/<id>` for the files it brings, plus whatever it adds to the
    manifest.
-2. The template directory itself, as **real files**. They are copied over the base, so an overlay replaces
-   a file rather than patching it, and template files stay valid TypeScript that an editor can check.
-   `_name` becomes `.name` on write, because npm strips a literal `.gitignore` out of a published tarball.
+2. The template directory itself, as **real files**. They are copied over the base, so an overlay replaces a
+   file rather than patching it, and template files stay valid TypeScript that an editor can check. `_name`
+   becomes `.name` on write, because npm strips a literal `.gitignore` out of a published tarball.
 3. A prompt in `src/cli.ts`, if it deserves a question of its own — and a flag, which it always does.
 
-`plan(answers)` is pure: answers in, a `Map` of path → contents out, no directory touched. That is what
-makes the whole matrix of options testable in milliseconds (`test/plan.test.mjs`) and `--dry-run` free. It
-is also exported, for a tool that wants to scaffold without the prompts:
+`plan(answers, pm)` is pure: answers in, a `Map` of path → contents out, no directory touched. That is what
+makes the whole matrix of options testable in milliseconds (`test/plan.test.mjs`) and `--dry-run` free. It is
+also exported, for a tool that wants to scaffold without the prompts:
 
 ```ts
 import { plan, writePlan } from '@rshono/create';
 ```
 
-## Two things worth knowing
-
-**The ESLint preset pins TypeScript 6.** Linting TypeScript with ESLint means `typescript-eslint`, which
-reads the compiler API directly rather than through a stable interface, so its peer range is
-`typescript >=4.8.4 <6.1.0` — below the TypeScript rshono is built and tested against. An app that chooses
-ESLint therefore gets `typescript ~6.0.3`, the newest that range allows: `npm install` would otherwise fail
-outright on the conflict, and forcing past it hands you a linter running against a compiler API it was never
-built for. The framework's declarations compile identically under either version, which is what makes this
-the app's pin and not the framework's — every other preset leaves TypeScript alone. What you trade for
-type-aware rules is a compiler one major behind, and the JavaScript implementation rather than the native
-one, so `typecheck` on a large app is several times slower. When upstream widens the range, the pin in
-`features/quality.ts` is the only thing to delete.
-
-**Tailwind is four packages, a `postcss.config.mjs` and one rule in `rshono.config.ts`.** rshono compiles
-CSS natively and has no PostCSS in it — that is deliberate, and it means an app that wants a plugin chain
-brings its own, through the `rspack` hook. The overlay writes all of it, with a comment saying what to
-delete to go back to plain CSS.
-
 ## Development
 
 ```bash
@@ -117,9 +122,13 @@ CREATE_RSHONO_E2E=1 pnpm --filter @rshono/create test   # also: pack, install an
 ```
 
 `plan.test.mjs` is the fast one — the whole matrix of answers in memory, no directory touched.
-`cli.test.mjs` spawns the real bin against temp directories, which is where argument parsing and the
-refusal to overwrite somebody's files are checked. `e2e.test.mjs` is the opt-in one, and the only one that
-installs anything.
+`cli.test.mjs` spawns the real bin against temp directories, which is where argument parsing and the refusal
+to overwrite somebody's files are checked. `e2e.test.mjs` is the opt-in one, and the only one that installs
+anything.
+
+`src/generated/framework.ts` — the rshono version, the Node range, the dependency pins and the deploy target
+list — is written by `scripts/codegen.mjs` from `packages/core`, so `pnpm --filter @rshono/create codegen` is
+what picks up a change there.
 
 `@clack/prompts` (MIT) is bundled rather than depended on, so `npx @rshono/create` downloads one tarball
 before it can ask its first question.

package/dist/api.mjs

@@ -79,7 +79,7 @@ __webpack_require__.d(__webpack_exports__, {
 
 ;// CONCATENATED MODULE: ./src/generated/framework.ts
 // GENERATED by scripts/codegen.mjs from packages/core — do not edit. Run `pnpm --filter @rshono/create codegen`.
-/** The framework release a scaffolded app is pinned to: this package and rshono ship together. */ const RSHONO_VERSION = '1.0.0-rc.6';
+/** The framework release a scaffolded app is pinned to: this package and rshono ship together. */ const RSHONO_VERSION = '1.0.0-rc.7';
 /**
  * The Node range rshono itself declares, restated in every scaffolded app's `engines` — so a CI image
  * or a contributor on an older Node hears it from their package manager rather than from a stack trace.

package/dist/cli.mjs

@@ -2943,7 +2943,7 @@ function hasGit(cwd) {
 
 ;// CONCATENATED MODULE: ./src/generated/framework.ts
 // GENERATED by scripts/codegen.mjs from packages/core — do not edit. Run `pnpm --filter @rshono/create codegen`.
-/** The framework release a scaffolded app is pinned to: this package and rshono ship together. */ const RSHONO_VERSION = '1.0.0-rc.6';
+/** The framework release a scaffolded app is pinned to: this package and rshono ship together. */ const RSHONO_VERSION = '1.0.0-rc.7';
 /**
  * The Node range rshono itself declares, restated in every scaffolded app's `engines` — so a CI image
  * or a contributor on an older Node hears it from their package manager rather than from a stack trace.
@@ -3840,7 +3840,7 @@ function fail(message) {
 async function main() {
     const { values, positionals } = parse();
     if (values.help) return console.log(HELP);
-    if (values.version) return console.log("1.0.0-rc.6");
+    if (values.version) return console.log("1.0.0-rc.7");
     /*
    * A pipe, a CI job or an agent gets the defaults rather than a prompt nothing can answer. Both streams
    * have to be a terminal: the prompts draw on stdout but *read from stdin*, so `echo | npx @rshono/create`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rshono/create",
-  "version": "1.0.0-rc.6",
+  "version": "1.0.0-rc.7",
   "description": "Scaffold a new rshono app — Hono + Rspack + React Server Components",
   "author": "Lasse <lasse@lassetange.com> (https://www.lassetange.com)",
   "license": "ISC",
@@ -46,7 +46,7 @@
     "@rspack/core": "2.1.5",
     "@types/node": "^26.1.1",
     "typescript": "^7.0.2",
-    "@rshono/core": "1.0.0-rc.6"
+    "@rshono/core": "1.0.0-rc.7"
   },
   "scripts": {
     "build": "node scripts/codegen.mjs && node scripts/build.mjs",