@absolutejs/absolute 0.20.0-beta.175 → 0.20.0-beta.177

package/CHANGELOG.md

@@ -6,6 +6,22 @@ This file is generated by `absolute-changelog` from the entries in
 `changelog/`. Edit an entry, not this file — and add new ones under
 `changelog/unreleased/`.
 
+## 0.20.0-beta.177 — 2026-11-14
+
+### Fixed
+
+- **A hot swap keeps shared resources open wherever `.use(networking)` sits in the app chain**
+  beta.176 kept an unchanged app's `onStop` from running on a hot swap, but only when `networking` was the last thing chained onto the app. `networking` swaps apps while the statement that builds the app is still running, so in `app.use(networking).onStop(shutdown)` the new app did not have its `onStop` yet when the hooks were compared. The swap decided the hooks had changed and shut the replaced app down, closing the database pool, audit log and queues the new app keeps. The swap now waits for that statement to finish before comparing, so the order of `.use(networking)` and the app's lifecycle hooks no longer matters.
+
+## 0.20.0-beta.176 — 2026-11-14
+
+### Fixed
+
+- **Deleting a server module no longer reports a failed hot update**
+  Deleting a server module logged "failed to update; the previous version keeps serving" with an ENOENT error, though nothing failed: there is nothing to apply, and the modules that imported it change through their own edits. A deleted module is now an unchanged outcome and logs nothing. Recreating it still applies as an edit.
+- **A hot swap no longer runs the app's shutdown hooks against resources the new app still uses**
+  Editing server code that rebuilds the app used to run the replaced app's `onStop` hooks on every hot swap. An `onStop` is usually the app's shutdown: it closes the database pool, the audit log and the queues, which unchanged top-level statements created and the new app keeps. After the swap the new app held closed resources, so routes that used them failed until the dev server was restarted. Lifecycle hooks are now treated like statements: when the new app's `onStart`/`onStop` hooks are the same code as the replaced app's, their effect carries across the swap and neither runs. Editing a hook still stops the old app and starts the new one, once each.
+
 ## 0.20.0-beta.175 — 2026-11-14
 
 ### Fixed

package/changelog.json

@@ -2,6 +2,33 @@
 	"contract": 1,
 	"name": "@absolutejs/absolute",
 	"releases": [
+		{
+			"changes": [
+				{
+					"detail": "beta.176 kept an unchanged app's `onStop` from running on a hot swap, but only when `networking` was the last thing chained onto the app. `networking` swaps apps while the statement that builds the app is still running, so in `app.use(networking).onStop(shutdown)` the new app did not have its `onStop` yet when the hooks were compared. The swap decided the hooks had changed and shut the replaced app down, closing the database pool, audit log and queues the new app keeps. The swap now waits for that statement to finish before comparing, so the order of `.use(networking)` and the app's lifecycle hooks no longer matters.",
+					"kind": "fixed",
+					"summary": "A hot swap keeps shared resources open wherever `.use(networking)` sits in the app chain"
+				}
+			],
+			"date": "2026-11-14",
+			"version": "0.20.0-beta.177"
+		},
+		{
+			"changes": [
+				{
+					"detail": "Deleting a server module logged \"failed to update; the previous version keeps serving\" with an ENOENT error, though nothing failed: there is nothing to apply, and the modules that imported it change through their own edits. A deleted module is now an unchanged outcome and logs nothing. Recreating it still applies as an edit.",
+					"kind": "fixed",
+					"summary": "Deleting a server module no longer reports a failed hot update"
+				},
+				{
+					"detail": "Editing server code that rebuilds the app used to run the replaced app's `onStop` hooks on every hot swap. An `onStop` is usually the app's shutdown: it closes the database pool, the audit log and the queues, which unchanged top-level statements created and the new app keeps. After the swap the new app held closed resources, so routes that used them failed until the dev server was restarted. Lifecycle hooks are now treated like statements: when the new app's `onStart`/`onStop` hooks are the same code as the replaced app's, their effect carries across the swap and neither runs. Editing a hook still stops the old app and starts the new one, once each.",
+					"kind": "fixed",
+					"summary": "A hot swap no longer runs the app's shutdown hooks against resources the new app still uses"
+				}
+			],
+			"date": "2026-11-14",
+			"version": "0.20.0-beta.176"
+		},
 		{
 			"changes": [
 				{

package/dist/angular/components/core/streamingSlotRegistrar.js

@@ -1,5 +1,5 @@
 // @bun
-// .angular-partial-tmp-0UabK1/src/core/streamingSlotRegistrar.ts
+// .angular-partial-tmp-DPRYTw/src/core/streamingSlotRegistrar.ts
 var STREAMING_SLOT_REGISTRAR_KEY = Symbol.for("absolutejs.streamingSlotRegistrar");
 var STREAMING_SLOT_WARNING_STORAGE_KEY = Symbol.for("absolutejs.streamingSlotWarningController");
 var STREAMING_SLOT_COLLECTION_STORAGE_KEY = Symbol.for("absolutejs.streamingSlotCollectionController");

package/dist/angular/components/core/streamingSlotRegistry.js

@@ -1,5 +1,5 @@
 // @bun
-// .angular-partial-tmp-0UabK1/src/core/streamingSlotRegistrar.ts
+// .angular-partial-tmp-DPRYTw/src/core/streamingSlotRegistrar.ts
 var STREAMING_SLOT_REGISTRAR_KEY = Symbol.for("absolutejs.streamingSlotRegistrar");
 var STREAMING_SLOT_WARNING_STORAGE_KEY = Symbol.for("absolutejs.streamingSlotWarningController");
 var STREAMING_SLOT_COLLECTION_STORAGE_KEY = Symbol.for("absolutejs.streamingSlotCollectionController");
@@ -46,7 +46,7 @@ var warnMissingStreamingSlotCollector = (primitiveName) => {
   getWarningController()?.maybeWarn(primitiveName);
 };
 
-// .angular-partial-tmp-0UabK1/src/core/streamingSlotRegistry.ts
+// .angular-partial-tmp-DPRYTw/src/core/streamingSlotRegistry.ts
 var STREAMING_SLOT_STORAGE_KEY = Symbol.for("absolutejs.streamingSlotAsyncLocalStorage");
 var isObjectRecord2 = (value) => Boolean(value) && typeof value === "object";
 var isAsyncLocalStorage = (value) => isObjectRecord2(value) && ("getStore" in value) && typeof value.getStore === "function" && ("run" in value) && typeof value.run === "function";

package/dist/build.js

@@ -38031,7 +38031,7 @@ var MAX_PROPAGATION_STEPS = 500, realPath4 = (path) => {
   if (typeof namespace !== "object" || namespace === null)
     throw new Error(`${path} did not evaluate to a module`);
   return Object.fromEntries(Object.entries(namespace));
-}, display = (path) => relative34(process.cwd(), path) || path, SLOW_UPDATE_MS = 500, SLOWEST_SHOWN = 3, statementLabel = (id) => {
+}, isMissingFile3 = (error) => error instanceof Error && ("code" in error) && error.code === "ENOENT", display = (path) => relative34(process.cwd(), path) || path, SLOW_UPDATE_MS = 500, SLOWEST_SHOWN = 3, statementLabel = (id) => {
   const name = id.slice(id.indexOf(":") + 1);
   return /^\d+$/.test(name) ? `statement #${name}` : name;
 }, slowestStatements = (modules) => modules.flatMap((module) => [...moduleRecord(module)?.lastTimings ?? []].map(([id, duration]) => ({
@@ -38074,6 +38074,8 @@ var MAX_PROPAGATION_STEPS = 500, realPath4 = (path) => {
   try {
     source = readFileSync56(path, "utf-8");
   } catch (error) {
+    if (isMissingFile3(error))
+      return { status: "unchanged" };
     reportFailure(path, error);
     return { error, status: "failed" };
   }
@@ -42094,5 +42096,5 @@ export {
   devBuild
 };
 
-//# debugId=70F4989EE77A073A64756E2164756E21
+//# debugId=2C9457EC4704C29664756E2164756E21
 //# sourceMappingURL=build.js.map