stonyx 0.2.3-alpha.63 → 0.2.3-alpha.65

package/README.md

@@ -13,12 +13,14 @@
 ## Quick Start
 
 ```bash
-npm install -g stonyx
+npm install -g stonyx@beta
 stonyx new my-app
 cd my-app
 stonyx serve
 ```
 
+Install from the `beta` channel: npm's `latest` tag still points at `0.2.2`, which predates the CLI (no `stonyx` binary, and its postinstall fails), and promoting a stable release is pending a release decision (abofs/stonyx#123). See [Why not `latest`](docs/modules.md#why-not-latest).
+
 The `new` command walks you through module selection and generates a ready-to-run project. From there, the CLI handles bootstrapping:
 
 ```bash
@@ -31,15 +33,15 @@ Stonyx reads `config/environment.ts` (preferred) or `config/environment.js`, ini
 
 ## Exports
 
-| Import path | What it exports |
-|-------------|-----------------|
-| `stonyx` | `Stonyx` class (default), `waitForModule(name)` |
-| `stonyx/config` | Live reference to the Stonyx config (default) |
-| `stonyx/log` | Live reference to the Chronicle logger (default) |
+| Import | Exports |
+|--------|---------|
+| `stonyx` | `Stonyx` class (default), `waitForModule(name)`; type `StoynxConfig` |
+| `stonyx/config` | The Stonyx config object (default), bound at first import |
+| `stonyx/log` | The Chronicle logger (default), bound at first import |
 | `stonyx/lifecycle` | `runStartupHooks(modules)`, `runShutdownHooks(modules)` |
 | `stonyx/test-helpers` | `setupIntegrationTests(hooks)` |
 
-`stonyx/config` and `stonyx/log` throw if read before Stonyx is initialized. See the [API Reference](docs/api.md) for details.
+`stonyx/config` and `stonyx/log` throw at import time if Stonyx is not yet initialized, so a static `import` of either fails the importing module even if the value is never read. Import them only from code that loads after bootstrap (your app code under `stonyx serve`, or a module's `init()` path). Their default export is bound once, at first import, so it does not follow an in-process reboot (see [Testing](docs/testing.md#booting-stonyx-more-than-once-in-one-process)). See the [API Reference](docs/api.md) for details.
 
 ## Documentation
 

package/dist/cli/new.js

@@ -234,7 +234,7 @@ export default config;
 }
 export function generateSetupTs() {
     return `// Test setup: bootstrap Stonyx with the consumer config before qunit runs.
-// Sprint 44 pattern — loaded via \`node --import ./test/setup.ts\`.
+// Loaded via \`node --import ./test/setup.ts\`.
 import { pathToFileURL } from 'url';
 
 const cwd = process.cwd();
@@ -371,7 +371,7 @@ export async function scaffoldProject(projectDir, appName, selectedModules) {
     await createFile(path.join(projectDir, 'test', 'acceptance', '.gitkeep'), '');
     // Create test config (TS)
     await createFile(path.join(projectDir, 'test', 'config', 'environment.ts'), generateTestEnvironmentTs());
-    // Create Sprint 44 test harness files (setup bootstraps Stonyx, zz-exit-test drains event loop)
+    // Create test harness files (setup bootstraps Stonyx, zz-exit-test drains event loop)
     await createFile(path.join(projectDir, 'test', 'setup.ts'), generateSetupTs());
     await createFile(path.join(projectDir, 'test', 'zz-exit-test.ts'), generateZzExitTestTs());
 }

package/dist/util/duplicate-core.js

@@ -1,5 +1,5 @@
 /**
- * Invariant I1 of the Sprint 93 install-and-boot cluster — "one core".
+ * Install-and-boot invariant I1 — "one core".
  *
  * At `Stonyx.start()`, every discovered module must resolve the SAME physical
  * `stonyx` package root as the running core. Otherwise the app has two

package/dist/util/import-config.d.ts

@@ -11,7 +11,7 @@ export declare const CONFIG_NOT_FOUND_PREFIX = "Config not found:";
  * with `CONFIG_NOT_FOUND_PREFIX`, because `main.ts`'s `NODE_ENV=test` catch
  * swallows that prefix and must not swallow this.
  *
- * This is invariant I2 of the Sprint 93 install-and-boot cluster — "no silent
+ * This is install-and-boot invariant I2 — "no silent
  * decline". Before #105 the two states were literally indistinguishable:
  * measured against `stonyx@0.2.3-beta.95`, a consumer with `config/environment.ts`
  * and the same consumer after `mv config/environment.js config/environment.xyz`

package/dist/util/import-config.js

@@ -43,7 +43,7 @@ export const CONFIG_NOT_FOUND_PREFIX = 'Config not found:';
  * with `CONFIG_NOT_FOUND_PREFIX`, because `main.ts`'s `NODE_ENV=test` catch
  * swallows that prefix and must not swallow this.
  *
- * This is invariant I2 of the Sprint 93 install-and-boot cluster — "no silent
+ * This is install-and-boot invariant I2 — "no silent
  * decline". Before #105 the two states were literally indistinguishable:
  * measured against `stonyx@0.2.3-beta.95`, a consumer with `config/environment.ts`
  * and the same consumer after `mv config/environment.js config/environment.xyz`

package/package.json

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