@c9up/aurora 0.1.37 → 0.1.38

package/dist/AuroraProvider.js

@@ -20,10 +20,12 @@ import { isAbsolute, resolve as resolvePath } from "node:path";
 import { fileURLToPath } from "node:url";
 import { AuroraManager } from "./AuroraManager.js";
 import { auroraRoute } from "./route.js";
-import { setAurora } from "./services/main.js";
+import { clearAurora, getAurora, setAurora } from "./services/main.js";
 import { renderToString } from "./ssr.js";
 export default class AuroraProvider {
     app;
+    /** What this provider bound, so shutdown only clears its own. */
+    #owned;
     constructor(app) {
         this.app = app;
     }
@@ -46,6 +48,7 @@ export default class AuroraProvider {
         // Force-resolve so `setAurora` runs even if the app never
         // touches the singleton from a preload.
         const manager = await this.app.container.resolve(AuroraManager);
+        this.#owned = manager;
         setAurora(manager);
     }
     async start() {
@@ -77,7 +80,15 @@ export default class AuroraProvider {
         }
     }
     async ready() { }
-    async shutdown() { }
+    async shutdown() {
+        // Release the module-level singleton, while it is still ours. A stopped
+        // application left a dead Aurora manager reachable through `services/main`, and
+        // with two applications in one process the survivor's binding must not
+        // be the one cleared.
+        if (this.#owned !== undefined && getAurora() === this.#owned)
+            clearAurora();
+        this.#owned = undefined;
+    }
     /**
      * Resolve the user-supplied config:
      *   - relative `pages.root` (e.g. `./resources/pages`) is joined to

package/dist/index.d.ts

@@ -1,4 +1,3 @@
-import "./augmentations.js";
 export type { CookieCodec, CookieOptions, PersistedSignalOptions, ShareData, StorageArea, WebStorageOptions, WindowSize, } from "./browser.js";
 export { back, booleanCookie, clipboard, cookie, cookieSignal, cookieState, forward, getCookieStore, hash, jsonCookie, mediaQuery, navigate, online, persistedSignal, prefersDark, queryParam, redirect, reload, replace, session, setCookieStore, share, storage, visibility, WebStorage, windowSize, } from "./browser.js";
 export { type ClassValue, clsx, cn, twMerge } from "./cn.js";

package/dist/index.js

@@ -4,7 +4,15 @@
 // node:fs / node:path / node:url live in `@c9up/aurora/server`. Keeping them off
 // this barrel is what lets a browser bundle import the client primitives without
 // the bundler dragging Node built-ins through the import graph.
-import "./augmentations.js";
+//
+// `./augmentations.js` is NOT loaded here either, and for a related reason: it
+// augments ream's HttpContext and ContainerBindings, so it names `@c9up/ream`
+// and drags ream's whole source into any program that imports this barrel. A
+// component library that only wants `component`/`html` was compiling ream's
+// decorated console commands under its own tsconfig, which does not enable
+// decorators — a build failure, in a package that never mentions ream. The
+// augmentations load from `@c9up/aurora/server` and `@c9up/aurora/provider`,
+// which is where every type they describe is reachable from anyway.
 export { back, booleanCookie, clipboard, cookie, cookieSignal, cookieState, forward, getCookieStore, hash, jsonCookie, mediaQuery, navigate, online, persistedSignal, prefersDark, queryParam, redirect, reload, replace, session, setCookieStore, share, storage, visibility, WebStorage, windowSize, } from "./browser.js";
 export { clsx, cn, twMerge } from "./cn.js";
 export { command } from "./command.js";

package/dist/server.d.ts

@@ -1,3 +1,4 @@
+import "./augmentations.js";
 export { AuroraManager, type AuroraManagerConfig } from "./AuroraManager.js";
 export { type AuroraRequestRenderer, auroraContext, } from "./middleware.js";
 export { type PageFactory, Pages, type PagesConfig } from "./Pages.js";

package/dist/server.js

@@ -4,6 +4,12 @@
 // importing client primitives (component/html/hydrate/render) never pulls the
 // Node built-ins through the import graph. Server code imports from
 // `@c9up/aurora/server`; the client `.` entry stays node-free.
+//
+// The ream augmentations (`ctx.aurora`, the `aurora` container binding) load
+// here rather than from the client barrel: everything they describe is
+// server-side, and naming `@c9up/ream` from the browser entry pulled ream's
+// source into every consumer's program — including ones that never use it.
+import "./augmentations.js";
 export { AuroraManager } from "./AuroraManager.js";
 export { auroraContext, } from "./middleware.js";
 export { Pages } from "./Pages.js";

package/dist/services/main.d.ts

@@ -14,5 +14,14 @@ import type { AuroraManager } from "../AuroraManager.js";
 export declare function setAurora(value: AuroraManager): void;
 /** @internal Read the singleton (or `undefined` pre-boot). */
 export declare function getAurora(): AuroraManager | undefined;
+/**
+ * @internal Release the singleton, so a shut-down application does not leave a
+ * dead Aurora manager reachable through `services/main`.
+ *
+ * The caller checks ownership first (`getAurora() === mine`): two applications
+ * share this module in one process, and the one shutting down must not clear
+ * what the other has since bound.
+ */
+export declare function clearAurora(): void;
 declare const aurora: AuroraManager;
 export default aurora;

package/dist/services/main.js

@@ -18,6 +18,17 @@ export function setAurora(value) {
 export function getAurora() {
     return instance;
 }
+/**
+ * @internal Release the singleton, so a shut-down application does not leave a
+ * dead Aurora manager reachable through `services/main`.
+ *
+ * The caller checks ownership first (`getAurora() === mine`): two applications
+ * share this module in one process, and the one shutting down must not clear
+ * what the other has since bound.
+ */
+export function clearAurora() {
+    instance = undefined;
+}
 const aurora = new Proxy({}, {
     get(_target, prop) {
         // A module loader inspects what it imports before anyone uses it: it reads

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c9up/aurora",
-  "version": "0.1.37",
+  "version": "0.1.38",
   "description": "Aurora — reactive UI runtime for the Ream framework. Tagged-template DOM, signal-based state, isomorphic SSR + hydration, zero build step.",
   "license": "MIT",
   "type": "module",

package/src/AuroraProvider.ts

@@ -26,7 +26,7 @@ import type {
 	AssetsRequest,
 	AssetsResponse,
 } from "./server/serveAssets.js";
-import { setAurora } from "./services/main.js";
+import { clearAurora, getAurora, setAurora } from "./services/main.js";
 import { renderToString } from "./ssr.js";
 
 interface AuroraContainer {
@@ -50,6 +50,9 @@ interface ReamRouter {
 }
 
 export default class AuroraProvider {
+	/** What this provider bound, so shutdown only clears its own. */
+	#owned: AuroraManager | undefined;
+
 	constructor(protected app: AuroraAppContext) {}
 
 	register(): void {
@@ -75,6 +78,7 @@ export default class AuroraProvider {
 		// touches the singleton from a preload.
 		const manager =
 			await this.app.container.resolve<AuroraManager>(AuroraManager);
+		this.#owned = manager;
 		setAurora(manager);
 	}
 
@@ -114,7 +118,14 @@ export default class AuroraProvider {
 	}
 
 	async ready(): Promise<void> {}
-	async shutdown(): Promise<void> {}
+	async shutdown(): Promise<void> {
+		// Release the module-level singleton, while it is still ours. A stopped
+		// application left a dead Aurora manager reachable through `services/main`, and
+		// with two applications in one process the survivor's binding must not
+		// be the one cleared.
+		if (this.#owned !== undefined && getAurora() === this.#owned) clearAurora();
+		this.#owned = undefined;
+	}
 
 	/**
 	 * Resolve the user-supplied config:

package/src/index.ts

@@ -4,7 +4,15 @@
 // node:fs / node:path / node:url live in `@c9up/aurora/server`. Keeping them off
 // this barrel is what lets a browser bundle import the client primitives without
 // the bundler dragging Node built-ins through the import graph.
-import "./augmentations.js";
+//
+// `./augmentations.js` is NOT loaded here either, and for a related reason: it
+// augments ream's HttpContext and ContainerBindings, so it names `@c9up/ream`
+// and drags ream's whole source into any program that imports this barrel. A
+// component library that only wants `component`/`html` was compiling ream's
+// decorated console commands under its own tsconfig, which does not enable
+// decorators — a build failure, in a package that never mentions ream. The
+// augmentations load from `@c9up/aurora/server` and `@c9up/aurora/provider`,
+// which is where every type they describe is reachable from anyway.
 
 export type {
 	CookieCodec,

package/src/server.ts

@@ -4,6 +4,12 @@
 // importing client primitives (component/html/hydrate/render) never pulls the
 // Node built-ins through the import graph. Server code imports from
 // `@c9up/aurora/server`; the client `.` entry stays node-free.
+//
+// The ream augmentations (`ctx.aurora`, the `aurora` container binding) load
+// here rather than from the client barrel: everything they describe is
+// server-side, and naming `@c9up/ream` from the browser entry pulled ream's
+// source into every consumer's program — including ones that never use it.
+import "./augmentations.js";
 
 export { AuroraManager, type AuroraManagerConfig } from "./AuroraManager.js";
 export {

package/src/services/main.ts

@@ -24,6 +24,18 @@ export function getAurora(): AuroraManager | undefined {
 	return instance;
 }
 
+/**
+ * @internal Release the singleton, so a shut-down application does not leave a
+ * dead Aurora manager reachable through `services/main`.
+ *
+ * The caller checks ownership first (`getAurora() === mine`): two applications
+ * share this module in one process, and the one shutting down must not clear
+ * what the other has since bound.
+ */
+export function clearAurora(): void {
+	instance = undefined;
+}
+
 const aurora: AuroraManager = new Proxy({} as AuroraManager, {
 	get(_target, prop) {
 		// A module loader inspects what it imports before anyone uses it: it reads