smbls 3.14.861 → 3.14.862

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # smbls
 
+## 3.14.862
+
+### Patch Changes
+
+- bfef7bf: `el.getAdoption()`: how an element's first view came, per element (XMA #501, ask A). `'adopted'` when its node is the built page's (a hydration boot); `'replaced'` when a replace boot built it in the first view over the built page and the built page had its counterpart (the same `data-key` chain, tag and rank — the match a replace already uses for the visitor's input); `null` for everything else: a fresh client render, a part the built page did not have, and every element made after the boot's first view (a navigation, a list's next data, an `if` that opens later). The value is set when the element's node is made, so it is there in `onRender` / `onInView` — in a replace, before the swap — and stays for the element's life. A replace answers `'replaced'`, never `'adopted'`, so a gate that waits for data still reads a fresh build; `el.context.prerendered` and `window.__BRENDER_HYDRATION__` stay the page-level signals. `getAdoption` is a built-in element method (utils `METHODS`): a shared library cannot replace it.
+- 0e57128: A language switch runs the create-time queries on screen again in the new language. When the root `lang` moves from one language to another (polyglot `setLang`, or a host that writes root `lang`), each element with create-time queries runs them again: a fresh entry for the new key answers from the cache, a request in flight on it is shared, otherwise one request per key. Before, nothing asked again until a window focus: the symbols.app landing switches a ka browser to Georgian in its root onRender, the switch waits for the Georgian font faces, and the home's reads went out in en and stayed English under a Georgian page (a picker switch after the load did the same). An answer for a key the declaration no longer asks for (its language, params or page moved since, and a newer run asks for the new key) is not taken, so an English reply that comes in after the switch never replaces the Georgian rows, and an old params' reply never replaces the new one.
+- 9f253fc: An element takes each answer once per declaration: one state write, one `transform`, one `onFetchComplete` (the element's and the config's). A window focus that joined the element's own request in flight handed it the answer a second time, and an older reply that found a newer request's rows in the cache handed those over again. A reply or a failure that comes in after a newer answer of the same key is not taken; a failure does not hold off the rows that come after it.
+- 9f253fc: A reconnect (window `online`) asks for each key once: the mounted queries refetch as a refresh, so several elements that read one key share one request. It ran forced, so the symbols.app home sent GET /core/presets once per declaration on every reconnect. A request that started before the reconnect is never joined, by the reconnect refetches or by a query that mounts after it. `refetchInterval`, `el.__ref.refetch()` and `fetchNextPage` stay forced.
+- de2f734: Lazy group parts per group (XMA #557, L1 + L2).
+
+  L1 — a group that uses none of the moved parts loads only its own chunk. `smbls build` now reads each `context.lazy` group's own code on its own (the files its entry reaches that the main code does not), and records which moved parts each group uses. The groups that use one go into the bundle as a number constant, `globalThis.__SMBLS_BUILD_LAZY_PARTS_GROUPS__`: bit `lazyPartsSlot(name)` (FNV-1a of the group name, mod 31) per group. The parcel transformer writes it at the flag's length, like the boolean flags, so the dist's source map still lines up (`buildFlags.json` gains `values`; `ensureSymbolsParcelConfig({ buildValues })`, `replaceBuildFlags(code, on, values)`). smbls wraps only those groups' loaders with the parts load. Two names can share a bit: that group then loads the parts too, as every group did before. No number (an older CLI writes `false`, a dev server leaves it unset), or a moved part no single group's code names: every group loads the parts, as before. The build line names each group: `… loaded with the first load of a group that uses them: inertOutside, TooltipLayer by admin, texts (no part: its own chunk only)`.
+
+  L2 — a page built with a group's page (`brender.lazyGroups`) whose group loads the parts preloads their file too, after the group's chunk: `smbls.core.lazyParts-<id>.esm.<hash>.js` as the bundler re-emits smbls's file, else the bundle whose source map lists smbls `src/lazyParts.js`. A build without that file warns; `build.modulePreload: "strict"` fails it.
+
+- d9194ce: Two new optional parts for `build.treeShakeFeatures` (XMA r12 results, item 3).
+
+  `routeHead` — the route entry's own head (K4, r12): utils `routeEntry.js` and `sharedLibraryBagEntry`, the router's same-page rule and the head it gives a swapped or kept page, helmet's `routeHead` hook and route-head layer. No word of the source decides it (every app spells `metadata`): the routes the build can read decide. They are the loaded pages, the app's own `routes`, every `routes` table of the app, its pages and components, and each lazy group's pages (the build loads the groups to read them). The build keeps the feature for a route entry that adds only a head to the component it names (`'/x': { extends: 'X', metadata: {…} }`), for two entries of one component (`'/a': 'X'` beside `'/b': { extends: 'X' }`), for an own head that merges with its component chain's metadata, for a head set as `helmet`, and when it cannot read the routes (a computed `routes`, a lazy group that does not load, a placeholder without `context.lazy`). String entries and pages with a head over a component without one leave it out. A project that calls an export of `routeEntry.js` keeps it. A build without it routes and shows heads as before K4 (each export of `routeEntry.js` answers as the readers did: the same page only when identical, the entry's own `metadata` or `helmet`), and an entry the feature would change that the build could not read (a stored or fetched page) logs one `console.error` naming `routeHead` and `build.treeShakeFeatures.keep`.
+
+  `themeColorList` — the `theme-color` list (`'theme-color': [{ content, media }, …]`, one meta per entry) in helmet and in the head builders (helmet `generateHeadHtml`, utils `generateMetaTags`). A build whose source sets `'theme-color'` only to a plain literal leaves it out; a list, a name or a call keeps it. The CLI's scan now reads a quoted key with a hyphen by its whole name (`'theme-color': …` and `meta['theme-color'] = …`). A list met at runtime (a fetched head) writes no tag and logs one `console.error`; served list tags stay as served. Node never sets the member, so a server render is unchanged. An older CLI keeps it for any `'theme-color'` string.
+
+  Bytes in an app bundle (a parcel production build of a small project, every other optional feature left out): both drops take out 2,974 B raw, 920 B gzip, 743 B Brotli. Each package bundled alone, minified and mangled (raw / Brotli): `routeHead` takes 1,192 / 423 out of `routeEntry.js` and 827 / 235 out of helmet; the router gains 159 / 83 (the check that reports an entry the build could not read). `themeColorList` takes 484 / 89 out of helmet.
+
+  The feature manifest gains `match.config` (the build's configuration rule decides the feature, on every build) and `broadStrings` (strings that keep the feature only for a CLI that does not know the exact rule). The build log's reason for a kept `routeHead` names the route (`config: route pages['/x'] adds only a head to X (the router keeps one page across such entries)`).
+
 ## 3.14.861
 
 ### Patch Changes