@absolutejs/absolute 0.20.0-beta.140 → 0.20.0-beta.143

package/CHANGELOG.md

@@ -6,6 +6,29 @@ 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.143 — 2026-10-22
+
+### Fixed
+
+- **Browser test recordings and reports no longer restart absolute dev**
+  Running a visible Playwright test with screenshots, video or tracing caused absolute dev to repeatedly restart the application: test-results, playwright-report, blob-report and .playwright-mcp were treated as source changes. These generated directories, including their creation and removal, are now ignored by the shared watcher. Atomic-write recovery also honors ignored paths, so temporary trace writes cannot reintroduce generated files into the rebuild queue. Real test source and application assets remain watched.
+- **`absolute dev` runs apps that import their own workspace packages, under Bun's isolated or hoisted linker, with hot reload**
+  An app that imports one of its own workspace packages (`"@acme/core": "workspace:*"`) did not run under `absolute dev`. With Bun's isolated linker, the default for a workspace, the dev build imported the package from the framework's own folder, could not find it, and the server crash-looped. With the hoisted linker the page rendered but never hydrated: modules outside the app's folder were addressed as `/@src/../…`, which a browser collapses before asking, so they 404ed. Now a package that resolves to source outside node_modules is the app's own code: served and transpiled like the app's files rather than vendored, its folder watched, and an edit to it hot-reloads in place (server and browser) instead of restarting the server or reloading the page. Packages are read from the app's folder, so any dependency only the app declares also works under the isolated linker, and the dev server serves files outside the app folder (a workspace package, a node_modules hoisted to the workspace root) through `/@src/@up/…`. A `dev.watchDirs` entry or a symlink written to work around this is no longer needed.
+- **Fresh installs declare the Elysia API version this release supports**
+  The broad prerelease peer range allowed Elysia 2.0.0-rc.0 and beta.32, which removed the request lifecycle method used by this framework release. The Elysia peer now requires 2.0.0-beta.21, matching the version used and verified by the framework. Fresh-package acceptance reads that peer contract instead of maintaining a separate stale Elysia range.
+
+## 0.20.0-beta.141 — 2026-10-19
+
+### Added
+
+- **Production serves brotli and gzip copies of static text assets, written at build time**
+  Production served every asset uncompressed, so browsers downloaded scripts, stylesheets and HTML files at full size: about three times the bytes, which on a slow network is most of the wait. Production builds now write brotli (quality 9) and gzip copies beside each text asset that compression shrinks by at least a tenth (about a second for the example app), and the production server sends a copy to a browser that accepts it, with `Content-Encoding`, the original `Content-Type`, `Vary: Accept-Encoding` and the asset's cache policy. React's vendor bundle goes from 181 KB to 53 KB. Nothing is compressed on the fly, so streamed responses (server-sent events, streamed pages) are untouched.
+
+### Fixed
+
+- **HEAD requests answer like GET (status and headers, no body) instead of 404**
+  Elysia 2 no longer answers HEAD for a GET route, so every AbsoluteJS app answered HEAD with 404 while GET answered 200, pages and static files alike. Uptime monitors, link checkers, crawlers and validators ask with HEAD and read that as down. `networking()` now adds a HEAD fallback that runs the request as GET and returns its status and headers without a body, compiled executables included. A route the app declares with `.head()` still wins.
+
 ## 0.20.0-beta.140 — 2026-10-18
 
 ### Fixed

package/changelog.json

@@ -2,6 +2,43 @@
 	"contract": 1,
 	"name": "@absolutejs/absolute",
 	"releases": [
+		{
+			"changes": [
+				{
+					"detail": "Running a visible Playwright test with screenshots, video or tracing caused absolute dev to repeatedly restart the application: test-results, playwright-report, blob-report and .playwright-mcp were treated as source changes. These generated directories, including their creation and removal, are now ignored by the shared watcher. Atomic-write recovery also honors ignored paths, so temporary trace writes cannot reintroduce generated files into the rebuild queue. Real test source and application assets remain watched.",
+					"kind": "fixed",
+					"summary": "Browser test recordings and reports no longer restart absolute dev"
+				},
+				{
+					"detail": "An app that imports one of its own workspace packages (`\"@acme/core\": \"workspace:*\"`) did not run under `absolute dev`. With Bun's isolated linker, the default for a workspace, the dev build imported the package from the framework's own folder, could not find it, and the server crash-looped. With the hoisted linker the page rendered but never hydrated: modules outside the app's folder were addressed as `/@src/../…`, which a browser collapses before asking, so they 404ed. Now a package that resolves to source outside node_modules is the app's own code: served and transpiled like the app's files rather than vendored, its folder watched, and an edit to it hot-reloads in place (server and browser) instead of restarting the server or reloading the page. Packages are read from the app's folder, so any dependency only the app declares also works under the isolated linker, and the dev server serves files outside the app folder (a workspace package, a node_modules hoisted to the workspace root) through `/@src/@up/…`. A `dev.watchDirs` entry or a symlink written to work around this is no longer needed.",
+					"kind": "fixed",
+					"summary": "`absolute dev` runs apps that import their own workspace packages, under Bun's isolated or hoisted linker, with hot reload"
+				},
+				{
+					"detail": "The broad prerelease peer range allowed Elysia 2.0.0-rc.0 and beta.32, which removed the request lifecycle method used by this framework release. The Elysia peer now requires 2.0.0-beta.21, matching the version used and verified by the framework. Fresh-package acceptance reads that peer contract instead of maintaining a separate stale Elysia range.",
+					"kind": "fixed",
+					"summary": "Fresh installs declare the Elysia API version this release supports"
+				}
+			],
+			"date": "2026-10-22",
+			"version": "0.20.0-beta.143"
+		},
+		{
+			"changes": [
+				{
+					"detail": "Elysia 2 no longer answers HEAD for a GET route, so every AbsoluteJS app answered HEAD with 404 while GET answered 200, pages and static files alike. Uptime monitors, link checkers, crawlers and validators ask with HEAD and read that as down. `networking()` now adds a HEAD fallback that runs the request as GET and returns its status and headers without a body, compiled executables included. A route the app declares with `.head()` still wins.",
+					"kind": "fixed",
+					"summary": "HEAD requests answer like GET (status and headers, no body) instead of 404"
+				},
+				{
+					"detail": "Production served every asset uncompressed, so browsers downloaded scripts, stylesheets and HTML files at full size: about three times the bytes, which on a slow network is most of the wait. Production builds now write brotli (quality 9) and gzip copies beside each text asset that compression shrinks by at least a tenth (about a second for the example app), and the production server sends a copy to a browser that accepts it, with `Content-Encoding`, the original `Content-Type`, `Vary: Accept-Encoding` and the asset's cache policy. React's vendor bundle goes from 181 KB to 53 KB. Nothing is compressed on the fly, so streamed responses (server-sent events, streamed pages) are untouched.",
+					"kind": "added",
+					"summary": "Production serves brotli and gzip copies of static text assets, written at build time"
+				}
+			],
+			"date": "2026-10-19",
+			"version": "0.20.0-beta.141"
+		},
 		{
 			"changes": [
 				{

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

@@ -1,5 +1,5 @@
 // @bun
-// .angular-partial-tmp-UKvYic/src/core/streamingSlotRegistrar.ts
+// .angular-partial-tmp-hyLGHB/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-UKvYic/src/core/streamingSlotRegistrar.ts
+// .angular-partial-tmp-hyLGHB/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-UKvYic/src/core/streamingSlotRegistry.ts
+// .angular-partial-tmp-hyLGHB/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";