@absolutejs/absolute 0.20.0-beta.179 → 0.20.0-beta.180

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.180 — 2026-11-14
+
+### Added
+
+- **`asset(manifest, key)` rejects keys the build does not write; `assetUnchecked` takes computed keys** (`asset`, `assetUnchecked`, `AbsoluteManifestKeys`, `ManifestKey`)
+  `asset(manifest, key)` accepted any string, so a misspelled key passed typecheck and failed at runtime. `absolute dev`, `absolute build` and `absolute typecheck` now derive the project's manifest keys from its pages, file routes, stylesheets and island registry, without building, and write `.absolutejs/types/manifest.d.ts`, which adds them to the new `AbsoluteManifestKeys` interface. `asset` takes a `ManifestKey`: one of those keys, or any string when the project has no generated file. The dev server rewrites the file when a page, stylesheet or island is added or removed. Keys that depend on bundling (a page's stylesheet, an island's stylesheet, a worker) are accepted whenever the build may write them, and shared chunks and self-hosted fonts are typed by pattern. For a key computed at runtime, use the new `assetUnchecked`: the same lookup without the check. `absolute typecheck` always reads the generated file; add `.absolutejs/types/manifest.d.ts` to `include` in tsconfig.json for the same check in your editor.
+
+### Fixed
+
+- **React pages with islands update on every edit and respond to clicks, and island edits keep island state**
+  On a React page that renders `<Island>`, edits to the page or to a component it imports logged "react component … applied" in `absolute dev` and changed nothing on screen. Beta.175 and beta.178 fixed real problems on that path (a missing island update, then two React updates per save), but not this one, and their tests passed because their pages loaded the page's own script before the islands bootstrap. In a real project it is usually the other way round: the bootstrap is one prebuilt file, while the page's script waits on every component the dev server transpiles. The bootstrap imports React DOM, and React DOM looks for the DevTools hook that Fast Refresh uses only once, when it loads. The page installed that hook afterwards, so Fast Refresh never found React DOM, and every refresh did nothing. The same ordering also broke clicks on the page (and can in production, where the scripts race the same way): React listens for events once per document, the first island root claimed that, and the page's root, created afterwards on the document, got no event listeners, so nothing outside the islands responded. In dev, pages with islands now install a stand-in DevTools hook before the bootstrap runs, so Fast Refresh finds React DOM whichever script loads first. Islands on a React page now wait for the page's root before they hydrate. Editing an island also no longer resets its state where the framework's own HMR keeps it: React islands use Fast Refresh, which keeps hook state unless the hooks changed, and Vue islands re-render in place after a template or style edit (a script edit reloads the component). Svelte islands still start over when edited, because Svelte's HMR recreates the component it swaps.
+- **Dev React Server Components pages no longer send file paths or server function source to the browser**
+  Under `absolute dev`, the Flight payload inlined into a React Server Components page (`self.__absoluteReactServerPayload`) carried React's development debug info: per server component its stack frames with absolute source paths (the project's and the framework's), its props, including the source text of function props such as a SuspenseSlot `resolve` callback, and timing rows. Dev renders now give React's Flight server a debug channel, so that info goes to a second stream that only the server-side HTML renderer reads; the payload sent to the browser keeps only references to it, which the Flight client skips. Stack frames are also dropped from error rows, so a server component error reaches the browser as its message, while the terminal still logs the full error. The page renders, streams and hydrates as before. In the browser, server components no longer appear in React DevTools or owner stacks, and server `console` calls are no longer replayed in the browser console; they still print in the terminal. Production payloads are unchanged.
+- **Dev picks up added and removed page routes without a restart**
+  The table of SPA routes the server answers (a path no page's router declares is a 404) was computed only by a full build, which `absolute dev` skips for page edits. A route added to a Vue page's `export const routes = defineRoutes([...])` kept answering 404 until dev restarted, a removed route kept rendering, and nothing was logged. The same was true of React `createBrowserRouter`, Svelte `<Router>` and Angular `provideRouter` route tables. Dev now re-reads an edited page's routes, updates the server's table and logs a `routes update` line naming the added and removed paths. A browser already on a Vue page swaps the new routes into its live router, so it can navigate to an added route without a full reload; if the route it is on was removed, it reloads and shows the 404. The route reader now also finds `defineRoutes` in a `<script>` block that follows `<script setup>`, which it previously missed.
+- **`absolute typecheck` passes with Vue and Svelte islands outside the framework directories, and checks their props**
+  `absolute typecheck` only knew about the `.vue` files under `vueDirectory` and generated Svelte declarations only for `svelteDirectory`, so a clean project whose island registry imports `./VueCounter.vue` or `./SvelteCounter.svelte` from `src/islands/` failed with TS2307 (Cannot find module). Every `.vue` and `.svelte` file in the project is now covered: Vue islands resolve for the plain checker and their props are checked by vue-check, Svelte islands get generated declarations and run through svelte-check, and a `.svelte` import no longer fails vue-check. Svelte 5 island props were also typed as `never` by `IslandRegistryProps` (and so by `createTypedIsland`); they are now the component's own props, so a wrong prop on a Svelte island is reported and a correct one passes.
+
+### Internal
+
+- **`startIslands` declares its options as a single parameter** (`startIslands`)
+  `startIslands` takes the same `StartIslandsOptions` object as before; its parameter is now declared as one `options` value instead of a destructured object, so on a React page it can wait for the page root before scheduling islands.
+
 ## 0.20.0-beta.179 — 2026-11-14
 
 ### Fixed

package/changelog.json

@@ -2,6 +2,51 @@
 	"contract": 1,
 	"name": "@absolutejs/absolute",
 	"releases": [
+		{
+			"changes": [
+				{
+					"detail": "On a React page that renders `<Island>`, edits to the page or to a component it imports logged \"react component … applied\" in `absolute dev` and changed nothing on screen. Beta.175 and beta.178 fixed real problems on that path (a missing island update, then two React updates per save), but not this one, and their tests passed because their pages loaded the page's own script before the islands bootstrap. In a real project it is usually the other way round: the bootstrap is one prebuilt file, while the page's script waits on every component the dev server transpiles. The bootstrap imports React DOM, and React DOM looks for the DevTools hook that Fast Refresh uses only once, when it loads. The page installed that hook afterwards, so Fast Refresh never found React DOM, and every refresh did nothing. The same ordering also broke clicks on the page (and can in production, where the scripts race the same way): React listens for events once per document, the first island root claimed that, and the page's root, created afterwards on the document, got no event listeners, so nothing outside the islands responded. In dev, pages with islands now install a stand-in DevTools hook before the bootstrap runs, so Fast Refresh finds React DOM whichever script loads first. Islands on a React page now wait for the page's root before they hydrate. Editing an island also no longer resets its state where the framework's own HMR keeps it: React islands use Fast Refresh, which keeps hook state unless the hooks changed, and Vue islands re-render in place after a template or style edit (a script edit reloads the component). Svelte islands still start over when edited, because Svelte's HMR recreates the component it swaps.",
+					"kind": "fixed",
+					"summary": "React pages with islands update on every edit and respond to clicks, and island edits keep island state"
+				},
+				{
+					"detail": "Under `absolute dev`, the Flight payload inlined into a React Server Components page (`self.__absoluteReactServerPayload`) carried React's development debug info: per server component its stack frames with absolute source paths (the project's and the framework's), its props, including the source text of function props such as a SuspenseSlot `resolve` callback, and timing rows. Dev renders now give React's Flight server a debug channel, so that info goes to a second stream that only the server-side HTML renderer reads; the payload sent to the browser keeps only references to it, which the Flight client skips. Stack frames are also dropped from error rows, so a server component error reaches the browser as its message, while the terminal still logs the full error. The page renders, streams and hydrates as before. In the browser, server components no longer appear in React DevTools or owner stacks, and server `console` calls are no longer replayed in the browser console; they still print in the terminal. Production payloads are unchanged.",
+					"kind": "fixed",
+					"summary": "Dev React Server Components pages no longer send file paths or server function source to the browser"
+				},
+				{
+					"detail": "The table of SPA routes the server answers (a path no page's router declares is a 404) was computed only by a full build, which `absolute dev` skips for page edits. A route added to a Vue page's `export const routes = defineRoutes([...])` kept answering 404 until dev restarted, a removed route kept rendering, and nothing was logged. The same was true of React `createBrowserRouter`, Svelte `<Router>` and Angular `provideRouter` route tables. Dev now re-reads an edited page's routes, updates the server's table and logs a `routes update` line naming the added and removed paths. A browser already on a Vue page swaps the new routes into its live router, so it can navigate to an added route without a full reload; if the route it is on was removed, it reloads and shows the 404. The route reader now also finds `defineRoutes` in a `<script>` block that follows `<script setup>`, which it previously missed.",
+					"kind": "fixed",
+					"summary": "Dev picks up added and removed page routes without a restart"
+				},
+				{
+					"detail": "`startIslands` takes the same `StartIslandsOptions` object as before; its parameter is now declared as one `options` value instead of a destructured object, so on a React page it can wait for the page root before scheduling islands.",
+					"kind": "internal",
+					"summary": "`startIslands` declares its options as a single parameter",
+					"symbols": [
+						"startIslands"
+					]
+				},
+				{
+					"detail": "`absolute typecheck` only knew about the `.vue` files under `vueDirectory` and generated Svelte declarations only for `svelteDirectory`, so a clean project whose island registry imports `./VueCounter.vue` or `./SvelteCounter.svelte` from `src/islands/` failed with TS2307 (Cannot find module). Every `.vue` and `.svelte` file in the project is now covered: Vue islands resolve for the plain checker and their props are checked by vue-check, Svelte islands get generated declarations and run through svelte-check, and a `.svelte` import no longer fails vue-check. Svelte 5 island props were also typed as `never` by `IslandRegistryProps` (and so by `createTypedIsland`); they are now the component's own props, so a wrong prop on a Svelte island is reported and a correct one passes.",
+					"kind": "fixed",
+					"summary": "`absolute typecheck` passes with Vue and Svelte islands outside the framework directories, and checks their props"
+				},
+				{
+					"detail": "`asset(manifest, key)` accepted any string, so a misspelled key passed typecheck and failed at runtime. `absolute dev`, `absolute build` and `absolute typecheck` now derive the project's manifest keys from its pages, file routes, stylesheets and island registry, without building, and write `.absolutejs/types/manifest.d.ts`, which adds them to the new `AbsoluteManifestKeys` interface. `asset` takes a `ManifestKey`: one of those keys, or any string when the project has no generated file. The dev server rewrites the file when a page, stylesheet or island is added or removed. Keys that depend on bundling (a page's stylesheet, an island's stylesheet, a worker) are accepted whenever the build may write them, and shared chunks and self-hosted fonts are typed by pattern. For a key computed at runtime, use the new `assetUnchecked`: the same lookup without the check. `absolute typecheck` always reads the generated file; add `.absolutejs/types/manifest.d.ts` to `include` in tsconfig.json for the same check in your editor.",
+					"kind": "added",
+					"summary": "`asset(manifest, key)` rejects keys the build does not write; `assetUnchecked` takes computed keys",
+					"symbols": [
+						"asset",
+						"assetUnchecked",
+						"AbsoluteManifestKeys",
+						"ManifestKey"
+					]
+				}
+			],
+			"date": "2026-11-14",
+			"version": "0.20.0-beta.180"
+		},
 		{
 			"changes": [
 				{

package/dist/angular/browser.js

@@ -88,7 +88,7 @@ var ABSOLUTE_HTTP_TRANSFER_CACHE_SKIP_HEADER = "x-skip-transfer-cache", buildAbs
 };
 
 // src/core/islandManifest.ts
-var ISLAND_BOOTSTRAP_MANIFEST_KEY = "AbsoluteIslandBootstrap", LEGACY_ISLAND_BOOTSTRAP_MANIFEST_KEY = "BootstrapClient", toIslandFrameworkSegment = (framework) => framework[0]?.toUpperCase() + framework.slice(1), collectFrameworkIslands = (manifest, prefix) => {
+var ISLAND_BOOTSTRAP_MANIFEST_KEY = "AbsoluteIslandBootstrap", LEGACY_ISLAND_BOOTSTRAP_MANIFEST_KEY = "BootstrapClient", REACT_PAGE_ROOT_EVENT = "absolute:react-page-root", toIslandFrameworkSegment = (framework) => framework[0]?.toUpperCase() + framework.slice(1), collectFrameworkIslands = (manifest, prefix) => {
   const entries = {};
   let found = false;
   for (const [key, value] of Object.entries(manifest)) {
@@ -10383,5 +10383,5 @@ export {
   withPendingTask
 };
 
-//# debugId=774C8D221132DC5A64756E2164756E21
+//# debugId=6ABD5809EADF708164756E2164756E21
 //# sourceMappingURL=browser.js.map