@absolutejs/absolute 0.20.0-beta.121 → 0.20.0-beta.123

package/CHANGELOG.md

@@ -6,6 +6,35 @@ 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.123 — 2026-09-28
+
+### Added
+
+- **React Fast Refresh keeps component state: `absolute dev` can run on AbsoluteJS's patched Bun**
+  Stock Bun ignores `reactFastRefresh` on `Bun.Transpiler` (oven-sh/bun#32919), so React edits in `absolute dev` remounted the page and lost component state. AbsoluteJS now publishes Bun 1.4.0 with just that fix for every platform Bun ships (github.com/absolutejs/patched-bun). In React projects on stock Bun, `absolute dev` offers it once (Install now / Ask me later / Don't ask again); it installs to ~/.absolutejs/bun, is checked against a pinned SHA-256, and only the dev server uses it, so your `bun` is unchanged. `absolute bun-patch [status|install|remove|reset]` manages it; `ABSOLUTE_PATCHED_BUN=0` opts out.
+
+### Fixed
+
+- **`absolute dev` keeps rebuilding after a syntax error in a React component or an unhandled rejection**
+  Under `bun --hot`, Bun counts unhandled rejections that no listener claims and never resets the count; while it is non-zero Bun parks the process in a loop that still serves requests and delivers file-watch events but never runs timers. The server entry imports React pages, so saving a React component with a syntax error made Bun's hot reload reject, and from then on the HMR debounce never fired: every edit was detected and queued, including the one that fixed the error, and nothing rebuilt until the dev server restarted. An unhandled rejection in app code did the same. The dev server now claims unhandled rejections and prints them as before, so its timers keep running.
+- **The patched Bun is now a release build, not a canary build**
+  `absolute bun-patch install` and the `absolute dev` offer now install `bun-v1.4.0-absolute.2`. The first release was built as a Bun canary build (Bun's build default): it reported `1.4.0-canary.1`, enabled Bun's experimental "bake" server features and made `bun upgrade` track canary. absolute.2 is built with `--canary=off`, as Bun's own releases are; the React Fast Refresh fix is unchanged. Run `absolute bun-patch install` to replace an absolute.1 install.
+- **Removed a React HMR CSS branch that only matched the example app**
+  The React HMR client had a CSS-only branch that looked up the example app's `ReactExampleCSS` manifest key, so it could never work in another app; the server never sends a CSS-only React update, so it was also unreachable. Removed. Stylesheet edits on React pages go through the general stylesheet swap, now covered by a browser test (the rule applies, component state and the document are kept).
+- **React edits that add a component, touch a hook or utility, or create a folder now update the page in place**
+  The React fast path told the browser to re-import a single module: the first non-page file in the batch. A new component added to the page re-imported only the new file, so the page never rendered it; a folder created alongside a file became the target and its URL failed to load; and an edited hook or utility whose importer had not been fetched through the module server re-imported just itself, which updates nothing on screen. Every edited file now gets a target (hooks and utilities resolve to the nearest importing component, falling back to the dependents the dependency graph found), directories and deleted paths are skipped, and the client imports them all before refreshing. On stock Bun the remount fallback rendered the changed child in place of the whole page; it now re-imports the page module for the page on screen and ignores edits that do not reach it.
+- **React Fast Refresh is used when Bun supports it, instead of always falling back to a remount**
+  The dev server decides between React Fast Refresh and the stock-Bun remount fallback by transpiling a probe component. The probe was named `__AbsoluteRefreshProbe`; React Fast Refresh registers only capitalized components, so it reported "unsupported" even on a Bun with the reactFastRefresh fix, and React edits always remounted with a warning. It now uses a capitalized name.
+- **A syntax error in a React component shows the error overlay instead of reloading the page**
+  A React edit that failed to compile was still broadcast as an update. The browser imported a module that answered 500 and fell back to a full reload, which showed the last good page and no error. The dev server now checks the edited modules compile first and sends the error overlay (file, line and source line) instead; the save that fixes it applies as a normal in-place update. The module server handler and its transform errors also moved to globalThis: after a `bun --hot` reload failed part-way, later imports of the module server got a fresh instance that was never configured, so pre-transforming the changed module silently did nothing.
+
+## 0.20.0-beta.122 — 2026-09-27
+
+### Fixed
+
+- **Preserve browser-translated attributes and inserted text-only font wrappers through hydration** (`captureSsrTextBaselines`, `prepareBrowserTranslationHydration`, `preserveBrowserTranslation`)
+  Snapshot alt, title, placeholder and aria-label alongside SSR text. Temporarily restore those attributes and newly inserted text-only font trees while the framework hydrates, then reapply translations on the hydrated nodes. Preserve authored and interactive markup, URLs, field values and genuine client changes. Fixes translated landing-page warnings and text reverting to English without suppressing ordinary hydration mismatches.
+
 ## 0.20.0-beta.121 — 2026-09-27
 
 ### Added

package/changelog.json

@@ -2,6 +2,63 @@
 	"contract": 1,
 	"name": "@absolutejs/absolute",
 	"releases": [
+		{
+			"changes": [
+				{
+					"detail": "Under `bun --hot`, Bun counts unhandled rejections that no listener claims and never resets the count; while it is non-zero Bun parks the process in a loop that still serves requests and delivers file-watch events but never runs timers. The server entry imports React pages, so saving a React component with a syntax error made Bun's hot reload reject, and from then on the HMR debounce never fired: every edit was detected and queued, including the one that fixed the error, and nothing rebuilt until the dev server restarted. An unhandled rejection in app code did the same. The dev server now claims unhandled rejections and prints them as before, so its timers keep running.",
+					"kind": "fixed",
+					"summary": "`absolute dev` keeps rebuilding after a syntax error in a React component or an unhandled rejection"
+				},
+				{
+					"detail": "`absolute bun-patch install` and the `absolute dev` offer now install `bun-v1.4.0-absolute.2`. The first release was built as a Bun canary build (Bun's build default): it reported `1.4.0-canary.1`, enabled Bun's experimental \"bake\" server features and made `bun upgrade` track canary. absolute.2 is built with `--canary=off`, as Bun's own releases are; the React Fast Refresh fix is unchanged. Run `absolute bun-patch install` to replace an absolute.1 install.",
+					"kind": "fixed",
+					"summary": "The patched Bun is now a release build, not a canary build"
+				},
+				{
+					"detail": "Stock Bun ignores `reactFastRefresh` on `Bun.Transpiler` (oven-sh/bun#32919), so React edits in `absolute dev` remounted the page and lost component state. AbsoluteJS now publishes Bun 1.4.0 with just that fix for every platform Bun ships (github.com/absolutejs/patched-bun). In React projects on stock Bun, `absolute dev` offers it once (Install now / Ask me later / Don't ask again); it installs to ~/.absolutejs/bun, is checked against a pinned SHA-256, and only the dev server uses it, so your `bun` is unchanged. `absolute bun-patch [status|install|remove|reset]` manages it; `ABSOLUTE_PATCHED_BUN=0` opts out.",
+					"kind": "added",
+					"summary": "React Fast Refresh keeps component state: `absolute dev` can run on AbsoluteJS's patched Bun"
+				},
+				{
+					"detail": "The React HMR client had a CSS-only branch that looked up the example app's `ReactExampleCSS` manifest key, so it could never work in another app; the server never sends a CSS-only React update, so it was also unreachable. Removed. Stylesheet edits on React pages go through the general stylesheet swap, now covered by a browser test (the rule applies, component state and the document are kept).",
+					"kind": "fixed",
+					"summary": "Removed a React HMR CSS branch that only matched the example app"
+				},
+				{
+					"detail": "The React fast path told the browser to re-import a single module: the first non-page file in the batch. A new component added to the page re-imported only the new file, so the page never rendered it; a folder created alongside a file became the target and its URL failed to load; and an edited hook or utility whose importer had not been fetched through the module server re-imported just itself, which updates nothing on screen. Every edited file now gets a target (hooks and utilities resolve to the nearest importing component, falling back to the dependents the dependency graph found), directories and deleted paths are skipped, and the client imports them all before refreshing. On stock Bun the remount fallback rendered the changed child in place of the whole page; it now re-imports the page module for the page on screen and ignores edits that do not reach it.",
+					"kind": "fixed",
+					"summary": "React edits that add a component, touch a hook or utility, or create a folder now update the page in place"
+				},
+				{
+					"detail": "The dev server decides between React Fast Refresh and the stock-Bun remount fallback by transpiling a probe component. The probe was named `__AbsoluteRefreshProbe`; React Fast Refresh registers only capitalized components, so it reported \"unsupported\" even on a Bun with the reactFastRefresh fix, and React edits always remounted with a warning. It now uses a capitalized name.",
+					"kind": "fixed",
+					"summary": "React Fast Refresh is used when Bun supports it, instead of always falling back to a remount"
+				},
+				{
+					"detail": "A React edit that failed to compile was still broadcast as an update. The browser imported a module that answered 500 and fell back to a full reload, which showed the last good page and no error. The dev server now checks the edited modules compile first and sends the error overlay (file, line and source line) instead; the save that fixes it applies as a normal in-place update. The module server handler and its transform errors also moved to globalThis: after a `bun --hot` reload failed part-way, later imports of the module server got a fresh instance that was never configured, so pre-transforming the changed module silently did nothing.",
+					"kind": "fixed",
+					"summary": "A syntax error in a React component shows the error overlay instead of reloading the page"
+				}
+			],
+			"date": "2026-09-28",
+			"version": "0.20.0-beta.123"
+		},
+		{
+			"changes": [
+				{
+					"detail": "Snapshot alt, title, placeholder and aria-label alongside SSR text. Temporarily restore those attributes and newly inserted text-only font trees while the framework hydrates, then reapply translations on the hydrated nodes. Preserve authored and interactive markup, URLs, field values and genuine client changes. Fixes translated landing-page warnings and text reverting to English without suppressing ordinary hydration mismatches.",
+					"kind": "fixed",
+					"summary": "Preserve browser-translated attributes and inserted text-only font wrappers through hydration",
+					"symbols": [
+						"captureSsrTextBaselines",
+						"prepareBrowserTranslationHydration",
+						"preserveBrowserTranslation"
+					]
+				}
+			],
+			"date": "2026-09-27",
+			"version": "0.20.0-beta.122"
+		},
 		{
 			"changes": [
 				{

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

@@ -1,7 +1,7 @@
 // @bun
 var __require = import.meta.require;
 
-// .angular-partial-tmp-yuN6Qt/src/core/streamingSlotRegistrar.ts
+// .angular-partial-tmp-TZvQHy/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,7 +1,7 @@
 // @bun
 var __require = import.meta.require;
 
-// .angular-partial-tmp-yuN6Qt/src/core/streamingSlotRegistrar.ts
+// .angular-partial-tmp-TZvQHy/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");
@@ -48,7 +48,7 @@ var warnMissingStreamingSlotCollector = (primitiveName) => {
   getWarningController()?.maybeWarn(primitiveName);
 };
 
-// .angular-partial-tmp-yuN6Qt/src/core/streamingSlotRegistry.ts
+// .angular-partial-tmp-TZvQHy/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/angular/index.js

@@ -1107,6 +1107,17 @@ var requireCurrentIslandRegistry = () => {
   globalThis.__absoluteIslandRegistry = registry;
 };
 
+// src/client/browserTranslationAttributes.ts
+var TRANSLATABLE_ATTRIBUTES;
+var init_browserTranslationAttributes = __esm(() => {
+  TRANSLATABLE_ATTRIBUTES = [
+    "alt",
+    "title",
+    "placeholder",
+    "aria-label"
+  ];
+});
+
 // src/core/browserTranslation.ts
 var BASELINE_MARKER = "__ABSOLUTE_SSR_TEXT_BASELINES__", BROWSER_TRANSLATION_BASELINE_SCRIPT, browserTranslationBaselineTag = () => `<script>${BROWSER_TRANSLATION_BASELINE_SCRIPT}</script>`, injectBrowserTranslationBaseline = (html) => {
   if (html.includes(BASELINE_MARKER))
@@ -1118,7 +1129,8 @@ var BASELINE_MARKER = "__ABSOLUTE_SSR_TEXT_BASELINES__", BROWSER_TRANSLATION_BAS
   return `${html.slice(0, closingBodyIndex)}${script}${html.slice(closingBodyIndex)}`;
 };
 var init_browserTranslation = __esm(() => {
-  BROWSER_TRANSLATION_BASELINE_SCRIPT = "window.__ABSOLUTE_SSR_TEXT_BASELINES__=new WeakMap();" + "{const r=document.body,b=window.__ABSOLUTE_SSR_TEXT_BASELINES__;" + 'if(r)for(const e of [r,...r.querySelectorAll("*")]){' + "const t=new Map();for(const [i,n]of[...e.childNodes].entries())" + 'if(n.nodeType===3)t.set(i,n.nodeValue??"");if(t.size)b.set(e,t);}}';
+  init_browserTranslationAttributes();
+  BROWSER_TRANSLATION_BASELINE_SCRIPT = "window.__ABSOLUTE_SSR_TEXT_BASELINES__=new WeakMap();" + "window.__ABSOLUTE_SSR_ATTRIBUTE_BASELINES__=new WeakMap();" + "{const r=document.body,b=window.__ABSOLUTE_SSR_TEXT_BASELINES__," + "a=window.__ABSOLUTE_SSR_ATTRIBUTE_BASELINES__;" + 'if(r)for(const e of [r,...r.querySelectorAll("*")]){' + "const t=new Map();for(const [i,n]of[...e.childNodes].entries())" + 'if(n.nodeType===3)t.set(i,n.nodeValue??"");if(t.size)b.set(e,t);' + `const v=new Map();for(const k of ${JSON.stringify(TRANSLATABLE_ATTRIBUTES)}){` + "const s=e.getAttribute(k);if(s!==null)v.set(k,s);}if(v.size)a.set(e,v);}}";
 });
 
 // src/angular/requestProviders.ts
@@ -16752,5 +16764,5 @@ export {
   withPendingTask
 };
 
-//# debugId=DE5F95BFF37D0BF264756E2164756E21
+//# debugId=E4722B59E349FBC764756E2164756E21
 //# sourceMappingURL=index.js.map