stonyx 0.2.3-alpha.49 → 0.2.3-alpha.50

package/dist/cli/new.d.ts

@@ -4,8 +4,31 @@ interface ModuleOption {
     dirs?: string[];
     files?: Record<string, () => string>;
 }
+export declare const MODULE_OPTIONS: ModuleOption[];
 export declare function generateDbSchema(): string;
-export declare function generatePackageJson(name: string, selectedModules: ModuleOption[]): string;
+/**
+ * The version of the `stonyx` package running this generator, read from its own
+ * `package.json` at call time.
+ *
+ * Read rather than hardcoded on purpose: a literal would be correct on the day
+ * it was written and silently stale on every day after (abofs/stonyx#113).
+ */
+export declare function readCoreVersion(): string;
+/**
+ * The npm dist-tag naming the release line a version belongs to:
+ * `0.2.3-beta.96` -> `beta`, `0.2.3-alpha.4` -> `alpha`, `0.2.2` -> `latest`.
+ *
+ * Every scaffolded `@stonyx/*` module is requested on the same line as the core
+ * that scaffolded it, so the generated project cannot mix a prerelease core with
+ * modules from the stable line (or the reverse).
+ *
+ * Bound: this assumes a prerelease identifier is also a published dist-tag name.
+ * True for `beta` and `alpha`, which are the only two lines the fleet publishes.
+ * A core released as e.g. `0.2.3-rc.1` with no `rc` dist-tag would scaffold an
+ * unresolvable module specifier -- loudly, at install, not silently.
+ */
+export declare function releaseTagFor(version: string): string;
+export declare function generatePackageJson(name: string, selectedModules: ModuleOption[], coreVersion?: string): string;
 export declare function generateAppTs(): string;
 export declare function generateEnvironmentTs(): string;
 export declare function generateTestEnvironmentTs(): string;

package/dist/cli/new.js

@@ -1,9 +1,10 @@
 import { confirm, prompt } from '@stonyx/utils/prompt';
 import { createFile, createDirectory, copyFile, fileExists } from '@stonyx/utils/file';
 import { spawn } from 'child_process';
+import { readFileSync } from 'fs';
 import path from 'path';
 import { fileURLToPath } from 'url';
-const MODULE_OPTIONS = [
+export const MODULE_OPTIONS = [
     {
         question: 'Will this project need a REST server?',
         package: '@stonyx/rest-server',
@@ -48,15 +49,61 @@ export default class DBModel extends Model {
 }
 `;
 }
-export function generatePackageJson(name, selectedModules) {
+/**
+ * The npm dist-tag that points at a package's stable release line. Only ever
+ * used as a *release line* selector for `@stonyx/*` modules (see
+ * `releaseTagFor`) -- never as the specifier for the core, which is always
+ * pinned exactly.
+ */
+const STABLE_DIST_TAG = 'latest';
+/** Absolute path to this package's own root, from both `src/` and `dist/`. */
+const packageRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..', '..');
+/**
+ * The version of the `stonyx` package running this generator, read from its own
+ * `package.json` at call time.
+ *
+ * Read rather than hardcoded on purpose: a literal would be correct on the day
+ * it was written and silently stale on every day after (abofs/stonyx#113).
+ */
+export function readCoreVersion() {
+    const raw = readFileSync(path.join(packageRoot, 'package.json'), 'utf8');
+    const version = JSON.parse(raw).version;
+    if (typeof version !== 'string' || !version) {
+        throw new Error(`Could not read the stonyx version from ${path.join(packageRoot, 'package.json')}`);
+    }
+    return version;
+}
+/**
+ * The npm dist-tag naming the release line a version belongs to:
+ * `0.2.3-beta.96` -> `beta`, `0.2.3-alpha.4` -> `alpha`, `0.2.2` -> `latest`.
+ *
+ * Every scaffolded `@stonyx/*` module is requested on the same line as the core
+ * that scaffolded it, so the generated project cannot mix a prerelease core with
+ * modules from the stable line (or the reverse).
+ *
+ * Bound: this assumes a prerelease identifier is also a published dist-tag name.
+ * True for `beta` and `alpha`, which are the only two lines the fleet publishes.
+ * A core released as e.g. `0.2.3-rc.1` with no `rc` dist-tag would scaffold an
+ * unresolvable module specifier -- loudly, at install, not silently.
+ */
+export function releaseTagFor(version) {
+    const prerelease = /^\d+\.\d+\.\d+-([0-9A-Za-z-]+)(?:\.|$)/.exec(version);
+    return prerelease ? prerelease[1] : STABLE_DIST_TAG;
+}
+export function generatePackageJson(name, selectedModules, coreVersion = readCoreVersion()) {
+    // The framework is a runtime dependency of the application, pinned exactly to
+    // the core that generated the project.
+    const dependencies = { stonyx: coreVersion };
     const devDependencies = {
         qunit: '^2.24.1',
-        stonyx: 'latest',
         tsx: '^4.21.0',
         typescript: '^5.8.3'
     };
+    // Modules are discovered from devDependencies (see docs/modules.md), and are
+    // requested on the core's own release line rather than at `latest`.
+    const moduleTag = releaseTagFor(coreVersion);
     for (const mod of selectedModules) {
-        devDependencies[mod.package] = 'latest';
+        devDependencies[mod.package] = moduleTag;
     }
     // Sort dependencies alphabetically
     const sorted = Object.fromEntries(Object.entries(devDependencies).sort(([a], [b]) => a.localeCompare(b)));
@@ -71,6 +118,7 @@ export function generatePackageJson(name, selectedModules) {
             start: 'stonyx serve',
             test: "NODE_ENV=test node --import tsx/esm --import ./test/setup.ts node_modules/qunit/bin/qunit.js 'test/**/*-test.ts'"
         },
+        dependencies,
         devDependencies: sorted
     }, null, 2) + '\n';
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "stonyx",
-  "version": "0.2.3-alpha.49",
+  "version": "0.2.3-alpha.50",
   "description": "Base stonyx framework module",
   "main": "dist/main.js",
   "types": "dist/main.d.ts",