create-ragen-app 0.2.0 → 0.4.0

package/dist/node-version.d.ts

@@ -0,0 +1,54 @@
+/**
+ * Whether this Node can be used to create a Ragen installation.
+ *
+ * The distinction that matters: **the installation** needs Node 24, not this
+ * CLI. The CLI itself runs happily on older majors — it was published and
+ * verified on Node 22 by accident — so refusing on the grounds that "this
+ * tool requires Node 24" would be both untrue and unhelpfully broad.
+ *
+ * What genuinely breaks is the first-run setup the wizard performs on the
+ * caller's behalf: `npm install` across the monorepo, `prisma generate`,
+ * `migrate deploy` and the seed all run under whatever Node invoked the
+ * wizard. Getting a half-built `node_modules` out of that is the expensive
+ * failure, because it surfaces much later and nowhere near its cause. npm's
+ * own `EBADENGINE` warning does fire, but as one line inside a wall of
+ * install output, and it does not say what will break.
+ *
+ * So the check is gated on what the wizard is about to *do*:
+ *
+ * - running the setup steps → refuse, before anything is cloned
+ * - `--skip-install` → proceed, because nothing runs here; warn instead,
+ *   since the scaffolded app still needs Node 24 to start
+ *
+ * `--yes` deliberately does not bypass it. That flag means "accept the
+ * defaults", not "ignore a requirement".
+ */
+/**
+ * Kept in step with this package's `engines.node` by
+ * `src/__tests__/node-version.test.ts`, and with the repository's own Node
+ * version documented in AGENTS.md ("Node.js 24.x (Active LTS)").
+ */
+export declare const REQUIRED_NODE_MAJOR = 24;
+export type NodeVersionVerdict = {
+    kind: 'ok';
+} | {
+    kind: 'warn';
+    message: string;
+} | {
+    kind: 'refuse';
+    message: string;
+};
+export interface NodeVersionCheck {
+    /** As `process.version` gives it, e.g. `v22.22.3`. */
+    version: string;
+    /** False when `--skip-install` means the wizard runs nothing itself. */
+    willRunSetup: boolean;
+}
+/**
+ * Returns undefined for anything that is not a recognisable Node version, so
+ * an unexpected format cannot be read as "too old" and block an install that
+ * would have worked.
+ */
+export declare function parseNodeMajor(version: string): number | undefined;
+export declare function checkNodeVersion({ version, willRunSetup, }: NodeVersionCheck): NodeVersionVerdict;
+//# sourceMappingURL=node-version.d.ts.map

package/dist/node-version.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"node-version.d.ts","sourceRoot":"","sources":["../src/node-version.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AAEH;;;;GAIG;AACH,eAAO,MAAM,mBAAmB,KAAK,CAAC;AAEtC,MAAM,MAAM,kBAAkB,GAC1B;IAAE,IAAI,EAAE,IAAI,CAAA;CAAE,GACd;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,GACjC;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE,CAAC;AAExC,MAAM,WAAW,gBAAgB;IAC/B,sDAAsD;IACtD,OAAO,EAAE,MAAM,CAAC;IAChB,wEAAwE;IACxE,YAAY,EAAE,OAAO,CAAC;CACvB;AAED;;;;GAIG;AACH,wBAAgB,cAAc,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,GAAG,SAAS,CAMlE;AAED,wBAAgB,gBAAgB,CAAC,EAC/B,OAAO,EACP,YAAY,GACb,EAAE,gBAAgB,GAAG,kBAAkB,CAkCvC"}

package/dist/node-version.js

@@ -0,0 +1,81 @@
+"use strict";
+/**
+ * Whether this Node can be used to create a Ragen installation.
+ *
+ * The distinction that matters: **the installation** needs Node 24, not this
+ * CLI. The CLI itself runs happily on older majors — it was published and
+ * verified on Node 22 by accident — so refusing on the grounds that "this
+ * tool requires Node 24" would be both untrue and unhelpfully broad.
+ *
+ * What genuinely breaks is the first-run setup the wizard performs on the
+ * caller's behalf: `npm install` across the monorepo, `prisma generate`,
+ * `migrate deploy` and the seed all run under whatever Node invoked the
+ * wizard. Getting a half-built `node_modules` out of that is the expensive
+ * failure, because it surfaces much later and nowhere near its cause. npm's
+ * own `EBADENGINE` warning does fire, but as one line inside a wall of
+ * install output, and it does not say what will break.
+ *
+ * So the check is gated on what the wizard is about to *do*:
+ *
+ * - running the setup steps → refuse, before anything is cloned
+ * - `--skip-install` → proceed, because nothing runs here; warn instead,
+ *   since the scaffolded app still needs Node 24 to start
+ *
+ * `--yes` deliberately does not bypass it. That flag means "accept the
+ * defaults", not "ignore a requirement".
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.REQUIRED_NODE_MAJOR = void 0;
+exports.parseNodeMajor = parseNodeMajor;
+exports.checkNodeVersion = checkNodeVersion;
+/**
+ * Kept in step with this package's `engines.node` by
+ * `src/__tests__/node-version.test.ts`, and with the repository's own Node
+ * version documented in AGENTS.md ("Node.js 24.x (Active LTS)").
+ */
+exports.REQUIRED_NODE_MAJOR = 24;
+/**
+ * Returns undefined for anything that is not a recognisable Node version, so
+ * an unexpected format cannot be read as "too old" and block an install that
+ * would have worked.
+ */
+function parseNodeMajor(version) {
+    const match = /^v?(\d+)\./.exec(version.trim());
+    if (!match) {
+        return undefined;
+    }
+    return Number(match[1]);
+}
+function checkNodeVersion({ version, willRunSetup, }) {
+    const major = parseNodeMajor(version);
+    if (major === undefined || major >= exports.REQUIRED_NODE_MAJOR) {
+        return { kind: 'ok' };
+    }
+    if (!willRunSetup) {
+        return {
+            kind: 'warn',
+            message: [
+                `You are on Node ${major}, and a Ragen installation needs Node ${exports.REQUIRED_NODE_MAJOR}.`,
+                'Nothing is being installed here, so the files will be written anyway —',
+                'but switch before running npm install or the app in the new directory.',
+            ].join(' '),
+        };
+    }
+    return {
+        kind: 'refuse',
+        message: [
+            `A Ragen installation needs Node ${exports.REQUIRED_NODE_MAJOR}, and this is Node ${major}.`,
+            '',
+            'Stopping before anything is written: the setup this runs for you —',
+            'npm install, prisma generate, migrate and seed — would run under this',
+            'Node and leave a tree that fails later, somewhere that does not point',
+            'back here.',
+            '',
+            `  nvm use ${exports.REQUIRED_NODE_MAJOR}   # or fnm, volta, asdf, …`,
+            '',
+            'Or pass --skip-install to write the files now and run the setup',
+            'yourself on a supported Node.',
+        ].join('\n'),
+    };
+}
+//# sourceMappingURL=node-version.js.map

package/dist/node-version.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"node-version.js","sourceRoot":"","sources":["../src/node-version.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;;;AA0BH,wCAMC;AAED,4CAqCC;AArED;;;;GAIG;AACU,QAAA,mBAAmB,GAAG,EAAE,CAAC;AActC;;;;GAIG;AACH,SAAgB,cAAc,CAAC,OAAe;IAC5C,MAAM,KAAK,GAAG,YAAY,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,CAAC;IAChD,IAAI,CAAC,KAAK,EAAE,CAAC;QACX,OAAO,SAAS,CAAC;IACnB,CAAC;IACD,OAAO,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC;AAC1B,CAAC;AAED,SAAgB,gBAAgB,CAAC,EAC/B,OAAO,EACP,YAAY,GACK;IACjB,MAAM,KAAK,GAAG,cAAc,CAAC,OAAO,CAAC,CAAC;IAEtC,IAAI,KAAK,KAAK,SAAS,IAAI,KAAK,IAAI,2BAAmB,EAAE,CAAC;QACxD,OAAO,EAAE,IAAI,EAAE,IAAI,EAAE,CAAC;IACxB,CAAC;IAED,IAAI,CAAC,YAAY,EAAE,CAAC;QAClB,OAAO;YACL,IAAI,EAAE,MAAM;YACZ,OAAO,EAAE;gBACP,mBAAmB,KAAK,yCAAyC,2BAAmB,GAAG;gBACvF,wEAAwE;gBACxE,wEAAwE;aACzE,CAAC,IAAI,CAAC,GAAG,CAAC;SACZ,CAAC;IACJ,CAAC;IAED,OAAO;QACL,IAAI,EAAE,QAAQ;QACd,OAAO,EAAE;YACP,mCAAmC,2BAAmB,sBAAsB,KAAK,GAAG;YACpF,EAAE;YACF,oEAAoE;YACpE,uEAAuE;YACvE,uEAAuE;YACvE,YAAY;YACZ,EAAE;YACF,aAAa,2BAAmB,6BAA6B;YAC7D,EAAE;YACF,iEAAiE;YACjE,+BAA+B;SAChC,CAAC,IAAI,CAAC,IAAI,CAAC;KACb,CAAC;AACJ,CAAC"}

package/dist/route-table.d.ts

@@ -0,0 +1,31 @@
+/** Where every app finds the table: `defaultRouteTablePath()` walks up to it. */
+export declare const ROUTE_TABLE_PATH = "infra/llm-gateway/routes.yaml";
+export interface RouteTableEntry {
+    /** The id the application asks for — `DEFAULT_MODEL`, `EMBEDDINGS_MODEL`. */
+    modelName: string;
+    /** A `@ragenai/llm-gateway` provider id. */
+    provider: string;
+    /** The upstream's own name for the model, which may differ from the id. */
+    model: string;
+}
+/**
+ * The route table for a scaffolded installation.
+ *
+ * Written **over** the table shipped in the repository rather than beside it,
+ * which is the same thing this wizard already does to
+ * `infra/litellm/config.yaml`. Two reasons, and the second is the one that
+ * decides it:
+ *
+ * - The shipped table names Azure, Bedrock, Vertex and Scaleway. A new
+ *   installation has credentials for none of them, so every entry in it is a
+ *   route to a 401.
+ * - `LLM_ROUTES_PATH` would be the alternative, and a *relative* one is a
+ *   trap: `routeTableFromEnv` joins it to `process.cwd()`, which is a
+ *   different directory for `apps/web`, `apps/api` and `apps/worker`. An
+ *   absolute path avoids that and then breaks the moment the directory is
+ *   moved. Writing the file where the default lookup already walks to it
+ *   needs no variable at all.
+ */
+export declare function renderRouteTable(entries: readonly RouteTableEntry[]): string;
+export declare function writeRouteTable(targetDir: string, entries: readonly RouteTableEntry[]): void;
+//# sourceMappingURL=route-table.d.ts.map

package/dist/route-table.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"route-table.d.ts","sourceRoot":"","sources":["../src/route-table.ts"],"names":[],"mappings":"AAGA,iFAAiF;AACjF,eAAO,MAAM,gBAAgB,kCAAkC,CAAC;AAEhE,MAAM,WAAW,eAAe;IAC9B,6EAA6E;IAC7E,SAAS,EAAE,MAAM,CAAC;IAClB,4CAA4C;IAC5C,QAAQ,EAAE,MAAM,CAAC;IACjB,2EAA2E;IAC3E,KAAK,EAAE,MAAM,CAAC;CACf;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,SAAS,eAAe,EAAE,GAAG,MAAM,CAyB5E;AAED,wBAAgB,eAAe,CAC7B,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,SAAS,eAAe,EAAE,GAClC,IAAI,CAEN"}

package/dist/route-table.js

@@ -0,0 +1,53 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ROUTE_TABLE_PATH = void 0;
+exports.renderRouteTable = renderRouteTable;
+exports.writeRouteTable = writeRouteTable;
+const node_fs_1 = require("node:fs");
+const node_path_1 = require("node:path");
+/** Where every app finds the table: `defaultRouteTablePath()` walks up to it. */
+exports.ROUTE_TABLE_PATH = 'infra/llm-gateway/routes.yaml';
+/**
+ * The route table for a scaffolded installation.
+ *
+ * Written **over** the table shipped in the repository rather than beside it,
+ * which is the same thing this wizard already does to
+ * `infra/litellm/config.yaml`. Two reasons, and the second is the one that
+ * decides it:
+ *
+ * - The shipped table names Azure, Bedrock, Vertex and Scaleway. A new
+ *   installation has credentials for none of them, so every entry in it is a
+ *   route to a 401.
+ * - `LLM_ROUTES_PATH` would be the alternative, and a *relative* one is a
+ *   trap: `routeTableFromEnv` joins it to `process.cwd()`, which is a
+ *   different directory for `apps/web`, `apps/api` and `apps/worker`. An
+ *   absolute path avoids that and then breaks the moment the directory is
+ *   moved. Writing the file where the default lookup already walks to it
+ *   needs no variable at all.
+ */
+function renderRouteTable(entries) {
+    const routes = entries
+        .map(({ modelName, provider, model }) => `  ${modelName}:\n    provider: ${provider}\n    model: ${model}\n`)
+        .join('');
+    return `# Written by create-ragen-app for this installation.
+#
+# Which upstream serves each model id the application asks for. Ragen calls
+# these providers itself — LLM_GATEWAY=native — with no proxy in the path.
+#
+# This replaced the table shipped in the repository, which routes to Azure,
+# Bedrock, Vertex and Scaleway. Those entries are not wrong, they are simply
+# not yours: nothing here has credentials for them.
+#
+# To serve another model, add an entry. The key is the id the application asks
+# for (DEFAULT_MODEL, EMBEDDINGS_MODEL, REPHRASE_MODEL); \`model\` is the
+# upstream's own name for it, which is not always the same string. Credentials
+# stay in the environment and never appear here.
+version: 1
+
+routes:
+${routes}`;
+}
+function writeRouteTable(targetDir, entries) {
+    (0, node_fs_1.writeFileSync)((0, node_path_1.join)(targetDir, exports.ROUTE_TABLE_PATH), renderRouteTable(entries));
+}
+//# sourceMappingURL=route-table.js.map

package/dist/route-table.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"route-table.js","sourceRoot":"","sources":["../src/route-table.ts"],"names":[],"mappings":";;;AAiCA,4CAyBC;AAED,0CAKC;AAjED,qCAAwC;AACxC,yCAAiC;AAEjC,iFAAiF;AACpE,QAAA,gBAAgB,GAAG,+BAA+B,CAAC;AAWhE;;;;;;;;;;;;;;;;;GAiBG;AACH,SAAgB,gBAAgB,CAAC,OAAmC;IAClE,MAAM,MAAM,GAAG,OAAO;SACnB,GAAG,CACF,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,EAAE,EAAE,CACjC,KAAK,SAAS,oBAAoB,QAAQ,gBAAgB,KAAK,IAAI,CACtE;SACA,IAAI,CAAC,EAAE,CAAC,CAAC;IAEZ,OAAO;;;;;;;;;;;;;;;;EAgBP,MAAM,EAAE,CAAC;AACX,CAAC;AAED,SAAgB,eAAe,CAC7B,SAAiB,EACjB,OAAmC;IAEnC,IAAA,uBAAa,EAAC,IAAA,gBAAI,EAAC,SAAS,EAAE,wBAAgB,CAAC,EAAE,gBAAgB,CAAC,OAAO,CAAC,CAAC,CAAC;AAC9E,CAAC"}

package/dist/storage-provider.d.ts

@@ -0,0 +1,49 @@
+/**
+ * Where uploaded documents live.
+ *
+ * The wizard skipped this until now and sent people to a manual guide, which
+ * is the one question where getting it wrong is expensive: `STORAGE_PROVIDER=s3`
+ * with a missing credential does not fail at boot in every app, it fails at
+ * the first upload, as a storage error three layers from the cause.
+ *
+ * The variable names and the config field names below mirror `STORAGE_SEAM` in
+ * `@ragenai/env`. They are copied rather than imported because this package is
+ * published to npm and `@ragenai/env` is private, so a dependency on it would
+ * make `npm create ragen-app` unresolvable. The copy is held to the original
+ * by `tests/architecture/create-ragen-app-knows-the-provider-seams.test.ts` —
+ * the same arrangement `manifest.ts` already has with the `.env.example`
+ * files.
+ */
+/**
+ * One field of a written config, and the variable it resolves from.
+ *
+ * `required` decides how the installer renders it: a required field is typed
+ * `string`, so it needs a fallback to compile, while an optional one takes
+ * `process.env.X` as it comes. Carrying it here rather than inferring from the
+ * name keeps the renderer from having a fourth opinion about which variables a
+ * provider needs.
+ */
+export interface ConfigField {
+    field: string;
+    envVar: string;
+    required: boolean;
+}
+export type StorageChoice = 'local' | 's3';
+export interface S3Answers {
+    bucket: string;
+    region: string;
+    accessKeyId: string;
+    secretAccessKey: string;
+    /** Blank selects AWS. Set for R2, Scaleway, MinIO or Ceph. */
+    endpoint: string;
+}
+export interface StorageSelection {
+    provider: StorageChoice;
+    /** Written to the root `.env.local` — credentials never go in the config. */
+    envUpdates: Record<string, string>;
+    /** The config fields, already named as the config names them. */
+    configFields: ConfigField[];
+}
+export declare const STORAGE_LABELS: Record<StorageChoice, string>;
+export declare function resolveStorageSelection(provider: StorageChoice, answers?: S3Answers): StorageSelection;
+//# sourceMappingURL=storage-provider.d.ts.map

package/dist/storage-provider.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"storage-provider.d.ts","sourceRoot":"","sources":["../src/storage-provider.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG;AAEH;;;;;;;;GAQG;AACH,MAAM,WAAW,WAAW;IAC1B,KAAK,EAAE,MAAM,CAAC;IACd,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,OAAO,CAAC;CACnB;AAED,MAAM,MAAM,aAAa,GAAG,OAAO,GAAG,IAAI,CAAC;AAE3C,MAAM,WAAW,SAAS;IACxB,MAAM,EAAE,MAAM,CAAC;IACf,MAAM,EAAE,MAAM,CAAC;IACf,WAAW,EAAE,MAAM,CAAC;IACpB,eAAe,EAAE,MAAM,CAAC;IACxB,8DAA8D;IAC9D,QAAQ,EAAE,MAAM,CAAC;CAClB;AAED,MAAM,WAAW,gBAAgB;IAC/B,QAAQ,EAAE,aAAa,CAAC;IACxB,6EAA6E;IAC7E,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACnC,iEAAiE;IACjE,YAAY,EAAE,WAAW,EAAE,CAAC;CAC7B;AAED,eAAO,MAAM,cAAc,EAAE,MAAM,CAAC,aAAa,EAAE,MAAM,CAGxD,CAAC;AAkBF,wBAAgB,uBAAuB,CACrC,QAAQ,EAAE,aAAa,EACvB,OAAO,CAAC,EAAE,SAAS,GAClB,gBAAgB,CAmDlB"}

package/dist/storage-provider.js

@@ -0,0 +1,84 @@
+"use strict";
+/**
+ * Where uploaded documents live.
+ *
+ * The wizard skipped this until now and sent people to a manual guide, which
+ * is the one question where getting it wrong is expensive: `STORAGE_PROVIDER=s3`
+ * with a missing credential does not fail at boot in every app, it fails at
+ * the first upload, as a storage error three layers from the cause.
+ *
+ * The variable names and the config field names below mirror `STORAGE_SEAM` in
+ * `@ragenai/env`. They are copied rather than imported because this package is
+ * published to npm and `@ragenai/env` is private, so a dependency on it would
+ * make `npm create ragen-app` unresolvable. The copy is held to the original
+ * by `tests/architecture/create-ragen-app-knows-the-provider-seams.test.ts` —
+ * the same arrangement `manifest.ts` already has with the `.env.example`
+ * files.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.STORAGE_LABELS = void 0;
+exports.resolveStorageSelection = resolveStorageSelection;
+exports.STORAGE_LABELS = {
+    local: 'Local filesystem (default — no cloud account needed)',
+    s3: 'S3-compatible (AWS, Cloudflare R2, Scaleway, MinIO, Ceph)',
+};
+/**
+ * A path-style endpoint is what Scaleway (dotted bucket names) and MinIO/Ceph
+ * need. Guessing it from the endpoint rather than asking keeps the wizard to
+ * one question per thing a person actually knows about their own storage.
+ */
+function needsPathStyle(endpoint) {
+    const host = endpoint.trim().toLowerCase();
+    if (!host) {
+        return false;
+    }
+    return (!host.includes('amazonaws.com') &&
+        !host.includes('r2.cloudflarestorage.com'));
+}
+function resolveStorageSelection(provider, answers) {
+    if (provider === 'local' || !answers) {
+        return {
+            provider: 'local',
+            envUpdates: { STORAGE_PROVIDER: 'local' },
+            configFields: [
+                { field: 'path', envVar: 'STORAGE_LOCAL_PATH', required: false },
+            ],
+        };
+    }
+    const endpoint = answers.endpoint.trim();
+    const envUpdates = {
+        STORAGE_PROVIDER: 's3',
+        S3_BUCKET_NAME: answers.bucket.trim(),
+        S3_REGION: answers.region.trim(),
+        S3_ACCESS_KEY_ID: answers.accessKeyId.trim(),
+        S3_SECRET_ACCESS_KEY: answers.secretAccessKey.trim(),
+    };
+    const configFields = [
+        { field: 'bucketName', envVar: 'S3_BUCKET_NAME', required: true },
+        { field: 'region', envVar: 'S3_REGION', required: true },
+        { field: 'accessKeyId', envVar: 'S3_ACCESS_KEY_ID', required: true },
+        {
+            field: 'secretAccessKey',
+            envVar: 'S3_SECRET_ACCESS_KEY',
+            required: true,
+        },
+    ];
+    if (endpoint) {
+        envUpdates.S3_ENDPOINT_URL = endpoint;
+        configFields.push({
+            field: 'endpoint',
+            envVar: 'S3_ENDPOINT_URL',
+            required: false,
+        });
+        if (needsPathStyle(endpoint)) {
+            envUpdates.S3_FORCE_PATH_STYLE = 'true';
+            configFields.push({
+                field: 'forcePathStyle',
+                envVar: 'S3_FORCE_PATH_STYLE',
+                required: false,
+            });
+        }
+    }
+    return { provider: 's3', envUpdates, configFields };
+}
+//# sourceMappingURL=storage-provider.js.map

package/dist/storage-provider.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"storage-provider.js","sourceRoot":"","sources":["../src/storage-provider.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;GAeG;;;AAyDH,0DAsDC;AA3EY,QAAA,cAAc,GAAkC;IAC3D,KAAK,EAAE,sDAAsD;IAC7D,EAAE,EAAE,2DAA2D;CAChE,CAAC;AAEF;;;;GAIG;AACH,SAAS,cAAc,CAAC,QAAgB;IACtC,MAAM,IAAI,GAAG,QAAQ,CAAC,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC;IAC3C,IAAI,CAAC,IAAI,EAAE,CAAC;QACV,OAAO,KAAK,CAAC;IACf,CAAC;IACD,OAAO,CACL,CAAC,IAAI,CAAC,QAAQ,CAAC,eAAe,CAAC;QAC/B,CAAC,IAAI,CAAC,QAAQ,CAAC,0BAA0B,CAAC,CAC3C,CAAC;AACJ,CAAC;AAED,SAAgB,uBAAuB,CACrC,QAAuB,EACvB,OAAmB;IAEnB,IAAI,QAAQ,KAAK,OAAO,IAAI,CAAC,OAAO,EAAE,CAAC;QACrC,OAAO;YACL,QAAQ,EAAE,OAAO;YACjB,UAAU,EAAE,EAAE,gBAAgB,EAAE,OAAO,EAAE;YACzC,YAAY,EAAE;gBACZ,EAAE,KAAK,EAAE,MAAM,EAAE,MAAM,EAAE,oBAAoB,EAAE,QAAQ,EAAE,KAAK,EAAE;aACjE;SACF,CAAC;IACJ,CAAC;IAED,MAAM,QAAQ,GAAG,OAAO,CAAC,QAAQ,CAAC,IAAI,EAAE,CAAC;IAEzC,MAAM,UAAU,GAA2B;QACzC,gBAAgB,EAAE,IAAI;QACtB,cAAc,EAAE,OAAO,CAAC,MAAM,CAAC,IAAI,EAAE;QACrC,SAAS,EAAE,OAAO,CAAC,MAAM,CAAC,IAAI,EAAE;QAChC,gBAAgB,EAAE,OAAO,CAAC,WAAW,CAAC,IAAI,EAAE;QAC5C,oBAAoB,EAAE,OAAO,CAAC,eAAe,CAAC,IAAI,EAAE;KACrD,CAAC;IAEF,MAAM,YAAY,GAAkB;QAClC,EAAE,KAAK,EAAE,YAAY,EAAE,MAAM,EAAE,gBAAgB,EAAE,QAAQ,EAAE,IAAI,EAAE;QACjE,EAAE,KAAK,EAAE,QAAQ,EAAE,MAAM,EAAE,WAAW,EAAE,QAAQ,EAAE,IAAI,EAAE;QACxD,EAAE,KAAK,EAAE,aAAa,EAAE,MAAM,EAAE,kBAAkB,EAAE,QAAQ,EAAE,IAAI,EAAE;QACpE;YACE,KAAK,EAAE,iBAAiB;YACxB,MAAM,EAAE,sBAAsB;YAC9B,QAAQ,EAAE,IAAI;SACf;KACF,CAAC;IAEF,IAAI,QAAQ,EAAE,CAAC;QACb,UAAU,CAAC,eAAe,GAAG,QAAQ,CAAC;QACtC,YAAY,CAAC,IAAI,CAAC;YAChB,KAAK,EAAE,UAAU;YACjB,MAAM,EAAE,iBAAiB;YACzB,QAAQ,EAAE,KAAK;SAChB,CAAC,CAAC;QAEH,IAAI,cAAc,CAAC,QAAQ,CAAC,EAAE,CAAC;YAC7B,UAAU,CAAC,mBAAmB,GAAG,MAAM,CAAC;YACxC,YAAY,CAAC,IAAI,CAAC;gBAChB,KAAK,EAAE,gBAAgB;gBACvB,MAAM,EAAE,qBAAqB;gBAC7B,QAAQ,EAAE,KAAK;aAChB,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IAED,OAAO,EAAE,QAAQ,EAAE,IAAI,EAAE,UAAU,EAAE,YAAY,EAAE,CAAC;AACtD,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ragen-app",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "private": false,
   "description": "Scaffold a self-hosted Ragen AI installation with one command",
   "license": "Apache-2.0",
@@ -22,7 +22,7 @@
   "scripts": {
     "build": "tsc -p tsconfig.json",
     "clean": "rm -rf dist",
-    "prepare": "npm run clean && npm run build",
+    "prepack": "npm run clean && npm run build",
     "lint": "eslint",
     "typecheck": "tsc --noEmit --incremental --tsBuildInfoFile ./typecheck.tsbuildinfo"
   },