@alxia/create 0.1.0 → 0.1.1

package/dist/templates/react-router.d.ts

@@ -1,26 +1,17 @@
 import type { Manifest } from '../registry';
-import { type AlxiaPackage } from '../versions';
+import type { AlxiaPackage } from '../versions';
 /**
- * The scaffold's command line: the newest `create-react-router` of the
- * highest React Router major `@alxia/react-router` accepts, with no prompt,
- * no install and no git repository — the install is ours, once alxia is in.
+ * Files the template stores under another name, because a published tarball
+ * would not hold them: `bun publish`, as `npm publish`, leaves every
+ * `.gitignore` out, and Bun leaves `bunfig.toml` out too.
  */
-export declare function scaffoldCommand(dir: string): string[];
-/** The scaffold is not what the edits expect: nothing more is written, and `main` removes it. */
-export declare class ScaffoldChanged extends Error {
-    constructor(file: string, expected: string);
-}
-export declare const BUNFIG = "[run]\n# The React Router CLI is a node script: this starts it on Bun, which\n# alxia's server needs, even where a node is installed.\nbun = true\n";
-/** `vite.config.ts` with `alxia()` after `reactRouter()`. */
-export declare function addPlugin(config: string): string;
-/** The manifest with alxia's dependencies and `start` on Bun. */
-export declare function addAlxia(manifest: Manifest, alxia: Record<AlxiaPackage, string>): Manifest;
+export declare const RENAMED: Readonly<Record<string, string>>;
 /**
- * Reads what the scaffold wrote in `dir` and checks it, without writing:
- * the manifest with alxia in, and the files to write beside it.
+ * The template in `dir`: its manifest, named `name` with alxia's packages at
+ * `alxia`'s ranges, and every other file, by the path it is written at.
  */
-export declare function alxiaLayer(dir: string, alxia: Record<AlxiaPackage, string>): Promise<{
+export declare function reactRouterTemplate(dir: string, name: string, alxia: Record<AlxiaPackage, string>): Promise<{
     manifest: Manifest;
-    files: Record<string, string>;
+    files: Record<string, Blob>;
 }>;
 //# sourceMappingURL=react-router.d.ts.map

package/dist/templates/react-router.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"react-router.d.ts","sourceRoot":"","sources":["../../src/templates/react-router.ts"],"names":[],"mappings":"AAUA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AAC5C,OAAO,EAAE,KAAK,YAAY,EAA6B,MAAM,aAAa,CAAC;AAE3E;;;;GAIG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,EAAE,CAUrD;AAED,iGAAiG;AACjG,qBAAa,eAAgB,SAAQ,KAAK;gBAC7B,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM;CAO1C;AAED,eAAO,MAAM,MAAM,wJAIlB,CAAC;AAIF,6DAA6D;AAC7D,wBAAgB,SAAS,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,CAmBhD;AAED,iEAAiE;AACjE,wBAAgB,QAAQ,CACvB,QAAQ,EAAE,QAAQ,EAClB,KAAK,EAAE,MAAM,CAAC,YAAY,EAAE,MAAM,CAAC,GACjC,QAAQ,CAuBV;AAQD;;;GAGG;AACH,wBAAsB,UAAU,CAC/B,GAAG,EAAE,MAAM,EACX,KAAK,EAAE,MAAM,CAAC,YAAY,EAAE,MAAM,CAAC,GACjC,OAAO,CAAC;IAAE,QAAQ,EAAE,QAAQ,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;CAAE,CAAC,CAiBhE"}
+{"version":3,"file":"react-router.d.ts","sourceRoot":"","sources":["../../src/templates/react-router.ts"],"names":[],"mappings":"AAUA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC;AAC5C,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,aAAa,CAAC;AAEhD;;;;GAIG;AACH,eAAO,MAAM,OAAO,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAGpD,CAAC;AAEF;;;GAGG;AACH,wBAAsB,mBAAmB,CACxC,GAAG,EAAE,MAAM,EACX,IAAI,EAAE,MAAM,EACZ,KAAK,EAAE,MAAM,CAAC,YAAY,EAAE,MAAM,CAAC,GACjC,OAAO,CAAC;IAAE,QAAQ,EAAE,QAAQ,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,IAAI,CAAC,CAAA;CAAE,CAAC,CAc9D"}

package/dist/versions.d.ts

@@ -14,8 +14,6 @@ export declare const PEER_RANGES: {
     readonly 'react-router': "^8.0.0";
     readonly vite: "^7.0.0 || ^8.0.0";
 };
-/** The highest major a range such as `^7.0.0 || ^8.0.0` names. */
-export declare function highestMajor(range: string): number;
 /**
  * The range a generated project declares for each `@alxia/*` package: what
  * this package's own `package.json` says. Published, that is `^<version>`,

package/dist/versions.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"versions.d.ts","sourceRoot":"","sources":["../src/versions.ts"],"names":[],"mappings":"AAQA,qDAAqD;AACrD,MAAM,MAAM,YAAY,GACrB,eAAe,GACf,aAAa,GACb,qBAAqB,CAAC;AAQzB;;;;;;;GAOG;AACH,eAAO,MAAM,WAAW;;;;;CAKd,CAAC;AAEX,kEAAkE;AAClE,wBAAgB,YAAY,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAMlD;AAED;;;;;;GAMG;AACH,wBAAsB,WAAW,CAChC,WAAW,GAAE,GAAiD,GAC5D,OAAO,CAAC,MAAM,CAAC,YAAY,EAAE,MAAM,CAAC,CAAC,CAcvC"}
+{"version":3,"file":"versions.d.ts","sourceRoot":"","sources":["../src/versions.ts"],"names":[],"mappings":"AAQA,qDAAqD;AACrD,MAAM,MAAM,YAAY,GACrB,eAAe,GACf,aAAa,GACb,qBAAqB,CAAC;AAQzB;;;;;;;GAOG;AACH,eAAO,MAAM,WAAW;;;;;CAKd,CAAC;AAEX;;;;;;GAMG;AACH,wBAAsB,WAAW,CAChC,WAAW,GAAE,GAAiD,GAC5D,OAAO,CAAC,MAAM,CAAC,YAAY,EAAE,MAAM,CAAC,CAAC,CAcvC"}

package/dist/write.d.ts

@@ -1,6 +1,7 @@
+/** Writes a template's project, its dependencies moved to the registry's newest. */
 import { type Template } from './args';
 import type { Io } from './io';
 import type { AlxiaPackage } from './versions';
-/** Writes the project into `target`; throws on a scaffold that changed. */
+/** Writes the project into `target`. */
 export declare function write(target: string, template: Template, alxia: Record<AlxiaPackage, string>, io: Io): Promise<true>;
 //# sourceMappingURL=write.d.ts.map

package/dist/write.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"write.d.ts","sourceRoot":"","sources":["../src/write.ts"],"names":[],"mappings":"AAGA,OAAO,EAAQ,KAAK,QAAQ,EAAE,MAAM,QAAQ,CAAC;AAC7C,OAAO,KAAK,EAAE,EAAE,EAAE,MAAM,MAAM,CAAC;AAK/B,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,YAAY,CAAC;AAE/C,2EAA2E;AAC3E,wBAAsB,KAAK,CAC1B,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,QAAQ,EAClB,KAAK,EAAE,MAAM,CAAC,YAAY,EAAE,MAAM,CAAC,EACnC,EAAE,EAAE,EAAE,GACJ,OAAO,CAAC,IAAI,CAAC,CAsCf"}
+{"version":3,"file":"write.d.ts","sourceRoot":"","sources":["../src/write.ts"],"names":[],"mappings":"AAAA,oFAAoF;AAIpF,OAAO,EAAQ,KAAK,QAAQ,EAAE,MAAM,QAAQ,CAAC;AAC7C,OAAO,KAAK,EAAE,EAAE,EAAE,MAAM,MAAM,CAAC;AAK/B,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,YAAY,CAAC;AAW/C,wCAAwC;AACxC,wBAAsB,KAAK,CAC1B,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,QAAQ,EAClB,KAAK,EAAE,MAAM,CAAC,YAAY,EAAE,MAAM,CAAC,EACnC,EAAE,EAAE,EAAE,GACJ,OAAO,CAAC,IAAI,CAAC,CAoCf"}

package/docs/README.md

@@ -2,11 +2,11 @@
 
 The [package README](../README.md) is the short version. This folder is the
 long one: what each template writes, what the `react-router` template
-changes in React Router's own, how the versions are chosen, and the errors
+adds to React Router's own, how the versions are chosen, and the errors
 the command prints.
 
 | Page | Read it when |
 | --- | --- |
 | [Guide](guide.md) | choosing a template, reading what it wrote, pinning or moving versions, or running the command in a script or CI |
-| [Troubleshooting](troubleshooting.md) | the command refused a directory, a template or an option, `create-react-router` changed, the registry did not answer, or `bun install` failed |
+| [Troubleshooting](troubleshooting.md) | the command refused a directory, a template or an option, the registry did not answer or lacked a version, or `bun install` failed |
 | [Roadmap](roadmap.md) | wondering what is coming, and what is not planned |

package/docs/guide.md

@@ -138,16 +138,12 @@ compile under each one, and under none.
 
 ## The `react-router` template
 
-It is React Router's template, not a copy of it: the command runs
-
-```sh
-bunx create-react-router@8 my-site --yes --no-install --no-git-init --no-agent-skills --no-motion
-```
-
-— the newest `create-react-router` of the React Router major
-`@alxia/react-router` accepts — and then makes the same small change
+It is React Router's official template, shipped inside this package and
+copied: what `create-react-router` wrote, committed as it wrote it, with the
+same small change
 [`examples/react-router`](https://github.com/softistx/alxia/tree/develop/examples/react-router)
-made to it, in code:
+made to it. Nothing is downloaded but the dependencies, and nothing runs
+before `bun install`. The change, against React Router's files:
 
 ```diff
  // package.json
@@ -156,7 +152,7 @@ made to it, in code:
 +    "start": "bun build/server/index.js",
    },
    "dependencies": {
-+    "@alxia/core": "^0.3.0",
++    "@alxia/core": "^0.3.1",
 +    "@alxia/react-router": "^0.2.0",
 ```
 
@@ -177,12 +173,19 @@ made to it, in code:
 bun = true
 ```
 
-Every other file is React Router's, as it wrote it. Each edit checks first
-that the file is the one it expects — `reactRouter()` once in `plugins`,
-the `dev`, `build` and `start` scripts, no `bunfig.toml` yet — and when
-React Router's template has changed, the command stops, removes what was
-written, and says which file
-([Troubleshooting](troubleshooting.md#create-alxia-create-react-routers--is-not-what-this-alxiacreate-expects-)).
+The `Dockerfile` is alxia's, in place of React Router's, which builds and
+runs on Node ([Docker](#docker)). Every other file is React Router's:
+`app/`, `public/`, `tsconfig.json`, `react-router.config.ts`, its
+`README.md` (with Bun's commands where it wrote npm's: `bun install`,
+`bun dev`, `bun run build`), `.gitignore` and `.dockerignore`. `package.json` takes the directory's name, and its
+versions are moved to the newest the registry has ([Versions](#versions)):
+the template's own are where they start.
+
+The template follows React Router's majors, not its every release: it is
+written again from `create-react-router` when React Router ships one that
+`@alxia/react-router` accepts, in a new `@alxia/create`. Between two, the
+files are what `create-react-router` wrote when the template was last
+generated (React Router 8.4.0 in this release), and the versions are the newest of that major.
 
 There is no `app/server.ts`: the plugin's default server serves the pages
 in `bun dev` and from the build. To put alxia's hooks or `/api` routes in
@@ -193,21 +196,39 @@ bunx alxia-react-router reveal
 ```
 
 The [`@alxia/react-router` guide](https://github.com/softistx/alxia/blob/develop/packages/react-router/docs/guide.md)
-goes from there. React Router's `Dockerfile` is kept as it wrote it, based
-on Node: deploy on Bun as that guide's
-[Deploying](https://github.com/softistx/alxia/blob/develop/packages/react-router/docs/guide.md#deploying)
-says.
+goes from there.
+
+### Docker
+
+The project's `Dockerfile` builds the app and runs it on Bun, on the
+official `oven/bun:1` image, in three stages: the production dependencies,
+then every dependency and `bun run build`, then an image with `build/`
+and the production `node_modules` alone, running
+`bun build/server/index.js`, `start`'s command, as the image's non-root
+`bun` user. `.dockerignore` keeps `node_modules`, `build` and
+`.react-router` out of the context.
+
+```sh
+cd my-site
+docker build -t my-site .
+docker run -p 3000:3000 my-site
+```
+
+The installs are `--frozen-lockfile`, from the `bun.lock` the command's
+`bun install` wrote: commit it. The commented file, and what to change to
+write files from the container, are in
+[`@alxia/react-router`'s guide](https://github.com/softistx/alxia/blob/develop/packages/react-router/docs/guide.md#docker).
 
 ## Versions
 
-A template is written with the versions it was written with, and React
-Router's lags behind its own releases. So before installing, the command
+A template ships the versions it was generated with, and React Router's
+lags behind its own releases. So before installing, the command
 asks the registry for every dependency's versions, and writes `^` the
 newest one alxia accepts:
 
 | dependency | moved to the newest within |
 | --- | --- |
-| `@alxia/core`, `@alxia/client`, `@alxia/react-router` | not moved: the versions this `@alxia/create` was published with |
+| `@alxia/core`, `@alxia/client`, `@alxia/react-router` | the ranges this `@alxia/create` was published with, such as `^0.3.1`; while the registry does not serve that version yet, the newest of its minor, `~0.3.0` |
 | `typescript` | `^6.0.3 \|\| ^7.0.0`, every alxia package's peer range |
 | `zod` | `^4.2.0`, `@alxia/zod`'s |
 | `vite` | `^7.0.0 \|\| ^8.0.0`, `@alxia/react-router`'s |
@@ -235,9 +256,19 @@ The registry is the one `BUN_CONFIG_REGISTRY` names, else
 that does not arrive keeps the template's version, and the command warns
 and goes on.
 
-alxia's own packages are not moved, so a project is always written with a
-set released together. `bunx @alxia/create@latest` takes the newest set;
-`bun update` moves an existing project's within its ranges.
+alxia's own packages stay within the ranges they were published with, so
+a project is always written with a set released together, and its patches
+since. `bunx @alxia/create@latest` takes the newest set; `bun update` moves
+an existing project's within its ranges.
+
+Right after a release, npm can take a few minutes to serve a version
+while the `@alxia/create` published beside it is already there. The
+command then writes the newest release of the same minor, whose `^` range
+takes the new version once it arrives, and says so:
+
+```
+  @alxia/core: the registry has no release within ^0.3.1 yet; wrote ^0.3.0, the newest of ~0.3.0
+```
 
 ## In a script or CI
 

package/docs/roadmap.md

@@ -15,23 +15,40 @@ Nothing scheduled yet.
 
 ## Later
 
-- **A Dockerfile on Bun for the `react-router` template.** React Router's
-  template ships one based on Node, which no longer runs the app once
-  `start` runs Bun; the
-  [`@alxia/react-router` guide](https://github.com/softistx/alxia/blob/develop/packages/react-router/docs/guide.md#deploying)
-  says what to change. The template keeps React Router's files as they are
-  written today, so this waits for a decision to edit more of them.
+Nothing scheduled yet.
 
 ## Not planned
 
-- **A copy of React Router's template.** The `react-router` template runs
-  React Router's own `create-react-router` and edits what it writes, as
-  `examples/react-router` was made: a frozen copy would drift from it.
+- **Running `create-react-router` at creation.** The template is its
+  output, committed and copied: a new project needs nothing but the
+  registry, and no change upstream can stop the command. It is generated
+  again from the scaffold when React Router ships a new major.
 - **A runtime dependency.** The prompts are Bun's `prompt()`, the registry
   is read with `fetch`, versions are compared with `Bun.semver`.
 
 ## Shipped
 
+### Next release
+
+- **The `react-router` template's `Dockerfile` runs on Bun.** It replaces
+  React Router's Node one: multi-stage on `oven/bun:1`, the production
+  dependencies apart, `bun run build`, then `bun build/server/index.js` as
+  the image's non-root `bun` user. `docker build` works in a new project
+  as it is.
+- **The `react-router` project's README runs Bun.** React Router's own
+  README, with `bun install`, `bun dev` and `bun run build` where it wrote
+  npm's commands.
+- **The `react-router` template is files, copied.** React Router's official
+  template ships inside `@alxia/create`, with alxia's layer, and is copied
+  as it is: no `create-react-router` runs, and no change in it can make the
+  command refuse.
+- **alxia's packages resolve at creation too.** `@alxia/core`,
+  `@alxia/client` and `@alxia/react-router` move to the newest version
+  within the ranges `@alxia/create` was published with. Right after a
+  release, while the registry does not serve that version yet, the newest
+  of the same minor is written, so `bun install` no longer fails with
+  `No version matching "^0.3.1"`.
+
 ### 0.1.0
 
 - `bun create @alxia [dir] [--template api|react-router] [--no-install]`,

package/docs/troubleshooting.md

@@ -26,17 +26,16 @@ nothing — the symptom.
 
 **Writing the project**
 
-- [`create-alxia: create-react-router's … is not what this @alxia/create expects: …`](#create-alxia-create-react-routers--is-not-what-this-alxiacreate-expects-)
-- [`create-alxia: failed: create-react-router exited with 1.`](#create-alxia-failed-create-react-router-exited-with-1)
 - [`create-alxia: failed: …`](#create-alxia-failed-)
 - [`create-alxia: warning: the registry did not answer for …; kept the versions the template ships.`](#create-alxia-warning-the-registry-did-not-answer-for--kept-the-versions-the-template-ships)
 - [`typescript: kept to ^6.0.3 || ^7.0.0, where the newest is 7.0.2; npm's latest, 8.0.0, is outside it`](#typescript-kept-to-603--700-where-the-newest-is-702-npms-latest-800-is-outside-it)
 - [`zod: no release within ^4.2.0; kept ^4.2.0`](#zod-no-release-within-420-kept-420)
+- [`@alxia/core: the registry has no release within ^0.3.1 yet; wrote ^0.3.0, the newest of ~0.3.0`](#alxiacore-the-registry-has-no-release-within-031-yet-wrote-030-the-newest-of-030)
 - [`create-alxia: bun install failed; the files are written.`](#create-alxia-bun-install-failed-the-files-are-written)
 
 **After**
 
-- [The `react-router` project's `docker build` fails](#the-react-router-projects-docker-build-fails)
+- [`error: lockfile had changes, but lockfile is frozen`](#error-lockfile-had-changes-but-lockfile-is-frozen)
 - [The project's `@alxia/*` are older than npm's latest](#the-projects-alxia-are-older-than-npms-latest)
 
 ## Before it runs
@@ -148,47 +147,6 @@ project beside it and move the files in.
 
 ## Writing the project
 
-### `create-alxia: create-react-router's … is not what this @alxia/create expects: …`
-
-**When:** the `react-router` template, after `create-react-router` ran.
-The message names the file — `package.json`, `vite.config.ts` or
-`bunfig.toml` — and what was expected of it:
-
-- `it is missing`: no `package.json` or `vite.config.ts`;
-- `react-router in its dependencies, and the scripts dev: react-router dev, build: react-router build and a start`;
-- `reactRouter() from "@react-router/dev/vite", called once in plugins: [...]`;
-- `it already imports @alxia/react-router/vite`;
-- `none, and there is one`: a `bunfig.toml` already.
-
-**Why:** React Router's template changed since this `@alxia/create` was
-released, and the edits that add alxia check each file before changing it
-rather than write a project that does not start. What was written is
-removed: the target directory is emptied when it was there, removed when
-it was not. A parent directory the command created for it, as `a/b` for
-`a/b/my-site`, stays.
-
-**Fix:** run the newest `@alxia/create`, whose edits follow the newest
-template:
-
-```sh
-bunx @alxia/create@latest my-site --template react-router
-```
-
-If that one refuses too, add alxia to React Router's template by hand, as
-[`@alxia/react-router`'s README](https://www.npmjs.com/package/@alxia/react-router)
-shows (`bun add`, `alxia()` in `vite.config.ts`, `start`), and open an
-issue.
-
-### `create-alxia: failed: create-react-router exited with 1.`
-
-**When:** the `react-router` template, when `create-react-router` itself
-failed; its own output, just above, says why. Most often the network:
-`bunx` could not fetch it, or it could not fetch React Router's template
-from GitHub.
-
-**Fix:** what its output says, then run the command again: what was
-written is removed.
-
 ### `create-alxia: failed: …`
 
 **When:** any other error while writing the project, with the error's own
@@ -196,7 +154,9 @@ message after `failed:` — most often the file system: `EACCES` writing
 into a directory the user cannot write to, `ENOSPC` with the disk full.
 
 **Fix:** what the message names, then run the command again: what was
-written is removed, as above.
+written is removed — the target directory is emptied when it was there,
+removed when it was not. A parent directory the command created for it, as
+`a/b` for `a/b/my-site`, stays.
 
 ### `create-alxia: warning: the registry did not answer for …; kept the versions the template ships.`
 
@@ -211,7 +171,10 @@ that is React Router's, whose TypeScript may be older than alxia accepts.
 
 **Fix:** once the registry answers, run the command again in an empty
 directory, or move the packages named within alxia's ranges by hand:
-`bun add -d typescript@^7 vite@^8`. Behind a proxy, check `BUN_CONFIG_REGISTRY` or
+`bun add -d typescript@^7 vite@^8`. The message can name an `@alxia/*`
+package too, on a mirror that does not hold alxia's: the range kept is the
+one this `@alxia/create` was published with, which that mirror cannot
+install either, so let it proxy npmjs.org. Behind a proxy, check `BUN_CONFIG_REGISTRY` or
 `npm_config_registry`, which the command reads.
 
 ### `typescript: kept to ^6.0.3 || ^7.0.0, where the newest is 7.0.2; npm's latest, 8.0.0, is outside it`
@@ -231,11 +194,27 @@ once the major is tested, and the next `@alxia/create` takes it.
 **When:** a notice: the registry answered for the package, but none of its
 releases is in the range alxia's packages accept — a registry mirror that
 holds only some versions, most often. The template's own version is kept.
+An `@alxia/*` package prints it too when the registry holds none of the
+range's minor, not even an older patch.
 
 **Fix:** check what the registry holds (`bun pm view zod versions`), let
 the mirror fetch the missing ones, or write a version within the range by
 hand after the project is created.
 
+### `@alxia/core: the registry has no release within ^0.3.1 yet; wrote ^0.3.0, the newest of ~0.3.0`
+
+**When:** a notice, not an error, right after an alxia release: the
+registry lists `@alxia/create`'s new version but not yet the
+`@alxia/core` (or `@alxia/client`, `@alxia/react-router`) published beside
+it. npm can take a few minutes to serve a version everywhere.
+
+**Why:** a project written with `^0.3.1` would fail its `bun install` with
+`No version matching "^0.3.1" found`. The command writes the newest release
+of the same minor instead; `^0.3.0` still takes 0.3.1.
+
+**Fix:** nothing to do. Once the registry serves the new version,
+`bun update @alxia/core` moves the project to it.
+
 ### `create-alxia: bun install failed; the files are written.`
 
 **When:** `bun install` exited non-zero in the new project; its output,
@@ -247,32 +226,34 @@ project is complete; only `node_modules` is missing.
 
 ## After
 
-### The `react-router` project's `docker build` fails
+### `error: lockfile had changes, but lockfile is frozen`
 
-**Symptom:** `COPY ./package.json package-lock.json /app/` finds no
-`package-lock.json`, or the image starts and `bun: not found`.
+**When:** `docker build` in a `react-router` project stops at
+`RUN bun install --frozen-lockfile`.
 
-**Why:** React Router's `Dockerfile` is kept as its template writes it: on
-Node, installed with npm. Once `start` runs `bun build/server/index.js`,
-it no longer fits.
+**Why:** the project's `Dockerfile` installs exactly what `bun.lock`
+records, and `package.json` now asks for something it does not: a
+dependency added or changed by hand, without `bun install`, or a `bun.lock` left
+behind in a clone where `package.json` moved on without it.
 
-**Fix:** base it on an `oven/bun` image, install with
-`bun install --production`, and make its command
-`bun build/server/index.js`, as
-[`@alxia/react-router`'s guide](https://github.com/softistx/alxia/blob/develop/packages/react-router/docs/guide.md#deploying)
-says.
+**Fix:** run `bun install`, commit `bun.lock`, and build again. The other
+traps of the image, a write refused to the `bun` user among them, are in
+[`@alxia/react-router`'s troubleshooting](https://github.com/softistx/alxia/blob/develop/packages/react-router/docs/troubleshooting.md#eacces-permission-denied-open-app).
 
 ### The project's `@alxia/*` are older than npm's latest
 
-**Symptom:** a fresh project declares `@alxia/core` at `^0.3.0` while npm
-has `0.4.0`.
+**Symptom:** a fresh project declares `@alxia/core` at `^0.3.4` while npm
+has `0.4.0`, and the output said `@alxia/core: kept to ^0.3.1, where the
+newest is 0.3.4; npm's latest, 0.4.0, is outside it`.
 
-**Why:** alxia's packages are written at the versions the `@alxia/create`
-that ran was published with ([Versions](guide.md#versions)), and a release
-of `@alxia/core` alone does not release a new `@alxia/create`.
+**Why:** alxia's packages move only within the ranges the `@alxia/create`
+that ran was published with ([Versions](guide.md#versions)): a new minor
+is outside them, and a release of `@alxia/core` alone does not release a
+new `@alxia/create`.
 
 **Fix:** `bunx @alxia/create@latest` for the newest `@alxia/create`, and in
 an existing project
-`bun add @alxia/core@latest @alxia/client@latest`, reading
+`bun add @alxia/core@latest @alxia/client@latest` (`api`) or
+`bun add @alxia/core@latest @alxia/react-router@latest` (`react-router`), reading
 [`@alxia/core`'s upgrading page](https://github.com/softistx/alxia/blob/develop/packages/core/docs/upgrading.md)
 for what a minor changed.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@alxia/create",
-	"version": "0.1.0",
+	"version": "0.1.1",
 	"description": "Start an alxia app: `bun create @alxia` writes an API with Zod, or React Router's official template served by alxia",
 	"license": "MIT",
 	"type": "module",
@@ -10,6 +10,7 @@
 	"files": [
 		"dist",
 		"docs",
+		"templates/react-router",
 		"README.md",
 		"package.json",
 		"LICENSE"
@@ -39,7 +40,7 @@
 	"devDependencies": {
 		"@alxia/client": "^0.2.1",
 		"@alxia/core": "^0.3.1",
-		"@alxia/react-router": "^0.2.0",
+		"@alxia/react-router": "^0.3.0",
 		"@types/bun": "^1.4.2",
 		"zod": "^4.6.5"
 	}

package/templates/react-router/.dockerignore

@@ -0,0 +1,4 @@
+.react-router
+build
+node_modules
+README.md

package/templates/react-router/Dockerfile

@@ -0,0 +1,29 @@
+# Bun builds the app and runs it: build/server/index.js is alxia's server,
+# which runs on Bun. Pinned to Bun 1, the major alxia supports.
+
+# The production dependencies alone, for the final image.
+FROM oven/bun:1 AS production-dependencies
+WORKDIR /app
+COPY package.json bun.lock* bunfig.toml* ./
+RUN bun install --frozen-lockfile --production
+
+# Every dependency, then react-router build: build/client and
+# build/server/index.js.
+FROM oven/bun:1 AS build
+WORKDIR /app
+COPY package.json bun.lock* bunfig.toml* ./
+RUN bun install --frozen-lockfile
+COPY . .
+RUN bun run build
+
+# The build and the production dependencies, run as Bun's own non-root
+# user. The server listens on PORT (3000) and HOST (0.0.0.0).
+FROM oven/bun:1
+WORKDIR /app
+ENV NODE_ENV=production
+COPY package.json ./
+COPY --from=production-dependencies /app/node_modules ./node_modules
+COPY --from=build /app/build ./build
+USER bun
+EXPOSE 3000
+CMD ["bun", "build/server/index.js"]

package/templates/react-router/README.md

@@ -0,0 +1,87 @@
+# Welcome to React Router!
+
+A modern, production-ready template for building full-stack React applications using React Router.
+
+[![Open in StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/github/remix-run/react-router-templates/tree/main/default)
+
+## Features
+
+- 🚀 Server-side rendering
+- ⚡️ Hot Module Replacement (HMR)
+- 📦 Asset bundling and optimization
+- 🔄 Data loading and mutations
+- 🔒 TypeScript by default
+- 🎉 TailwindCSS for styling
+- 📖 [React Router docs](https://reactrouter.com/)
+
+## Getting Started
+
+### Installation
+
+Install the dependencies:
+
+```bash
+bun install
+```
+
+### Development
+
+Start the development server with HMR:
+
+```bash
+bun dev
+```
+
+Your application will be available at `http://localhost:5173`.
+
+## Building for Production
+
+Create a production build:
+
+```bash
+bun run build
+```
+
+## Deployment
+
+### Docker Deployment
+
+To build and run using Docker:
+
+```bash
+docker build -t my-app .
+
+# Run the container
+docker run -p 3000:3000 my-app
+```
+
+The containerized application can be deployed to any platform that supports Docker, including:
+
+- AWS ECS
+- Google Cloud Run
+- Azure Container Apps
+- Digital Ocean App Platform
+- Fly.io
+- Railway
+
+### DIY Deployment
+
+The build is production-ready: `bun run start` runs `build/server/index.js` on Bun.
+
+Make sure to deploy the output of `bun run build`
+
+```
+├── package.json
+├── bun.lock
+├── build/
+│   ├── client/    # Static assets
+│   └── server/    # Server-side code
+```
+
+## Styling
+
+This template comes with [Tailwind CSS](https://tailwindcss.com/) already configured for a simple default starting experience. You can use whatever CSS framework you prefer.
+
+---
+
+Built with ❤️ using React Router.

package/templates/react-router/_bunfig.toml

@@ -0,0 +1,4 @@
+[run]
+# The React Router CLI is a node script: this starts it on Bun, which
+# alxia's server needs, even where a node is installed.
+bun = true

package/templates/react-router/app/app.css

@@ -0,0 +1,15 @@
+@import "tailwindcss";
+
+@theme {
+  --font-sans: "Inter", ui-sans-serif, system-ui, sans-serif,
+    "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji";
+}
+
+html,
+body {
+  @apply bg-white dark:bg-gray-950;
+
+  @media (prefers-color-scheme: dark) {
+    color-scheme: dark;
+  }
+}