@nifrajs/web-solid 5.1.0 → 5.2.0

package/CHANGELOG.md

@@ -0,0 +1,1251 @@
+# @nifrajs/web-solid
+
+## 5.2.0
+
+### Minor Changes
+
+- 1d20d1f: An app registers its locale routing once: `export const i18n = urls` (the router `defineI18nRouting()` returns) from `backend/framework.ts`, which `nifra dev`, `nifra build` and the generated server entry pass to `createWebApp({ i18n })`. Every document then takes `<html lang dir>` from the registry's `documentMeta(localeOf(path))` unless the route's meta sets `lang`, on a hard load and after each client navigation, and carries `Content-Language`. Each adapter's new `useLocale()` returns the page's locale key, and `<I18nProvider>` formats in the page's locale when no `locale` is passed, with no loader handing either over. A route under a `[lang]` or `[[lang]]` directory runs `matchSegment()` before any middleware: an unserved locale, or a page missing from it, is a 404 through the app's `_404`, and a non-canonical prefix such as `/en/x` with an unprefixed default is a 308 to `/x`.
+
+### Patch Changes
+
+- 9498cf8: The package ships its `CHANGELOG.md`, so the installed package has the notes for every version, as the GitHub release does. Before, the tarball held only the code, `README.md`, `LICENSE` and `package.json`.
+- 281a48e: A production client build (Bun or Vite) moves copy tables (`@nifrajs/i18n/copy`) into one chunk per locale, so a page's JavaScript carries the copy of the locale it renders in and none of the others; the server bundle keeps every table whole. The client manifest lists the chunks as `copyChunks`, the generated server entry passes them to the new `createWebApp({ copyChunks })` option (a hand-written entry passes the manifest's), and each page hands the map to the browser and preloads the chunks it reads: its URL's locale and the one its `<html lang>` names. A client navigation loads the next URL's chunk with the route's code; the router passes the target path to `loadModule` for that. The build reads tables with the app's TypeScript (5.9 or 6) and warns and leaves them whole without one; `buildClient({ copySplit: false })` turns it off. `readSource()` and `addSourceTransform()` in `@nifrajs/web/plugins/kit` let a plugin that claims a file still compile the rewritten source; the Solid and StyleX plugins read through it.
+- Updated dependencies [9498cf8]
+- Updated dependencies [1f3ff32]
+- Updated dependencies [4bb8e52]
+- Updated dependencies [cdff19d]
+- Updated dependencies [5edd0ba]
+- Updated dependencies [000b4cb]
+- Updated dependencies [c5455fb]
+- Updated dependencies [6082ba5]
+- Updated dependencies [fd58beb]
+- Updated dependencies [ea25a61]
+- Updated dependencies [ed13e36]
+- Updated dependencies [281a48e]
+- Updated dependencies [281a48e]
+- Updated dependencies [1d20d1f]
+- Updated dependencies [1d20d1f]
+- Updated dependencies [746ada9]
+- Updated dependencies [1d20d1f]
+- Updated dependencies [b9e7c6b]
+  - @nifrajs/core@5.2.0
+  - @nifrajs/i18n@5.2.0
+  - @nifrajs/image@5.2.0
+  - @nifrajs/web@5.2.0
+
+## 5.1.0
+
+### Patch Changes
+
+- df50368: When a Solid `<ErrorBoundary>` catches during server rendering, or a resource fails, the page no longer ships the error's message and stack in its inline hydration script. On Bun, that also included the server file path. The browser now receives `Error("Internal Server Error")`. In development and test the error keeps its text. That inline script now also carries the document's CSP nonce on pages rendered in one pass: `RenderAdapter.renderToString` receives `{ nonce }` as `renderToStream` already did. Before, a strict CSP blocked the script and hydration did not match the server's markup.
+- Updated dependencies [78b2a04]
+- Updated dependencies [638efe5]
+- Updated dependencies [2a0a5d3]
+- Updated dependencies [5372e3a]
+- Updated dependencies [b276c67]
+- Updated dependencies [29d6649]
+- Updated dependencies [2a0a5d3]
+- Updated dependencies [72e1b4b]
+- Updated dependencies [7bb8a67]
+- Updated dependencies [513ec28]
+  - @nifrajs/web@5.1.0
+  - @nifrajs/core@5.1.0
+  - @nifrajs/i18n@5.1.0
+  - @nifrajs/image@5.1.0
+
+## 5.0.0
+
+### Minor Changes
+
+- fc0284a: Add opt-in server components across React, Vue, Svelte, Solid and Preact. Closed schemas project public props, owner GET admission and read capabilities govern every refresh, and private responses bypass shared caches. React uses native Flight; Vue, Svelte, Solid and Preact preserve native island state and owned ranges.
+
+  Add coordinated Vite builds and development generations, guarded component references, generated Bun/Node/Deno/Workers/Pages/Vercel outputs, typed outlets, router and server-function refresh integration, and release certification for browsers, packaged consumers, resource limits and performance. Existing applications retain their default rendering pipeline.
+
+  Reuse registered Web middleware continuations across requests while retaining request-local state.
+
+### Patch Changes
+
+- Updated dependencies [7169820]
+- Updated dependencies [22e3df7]
+- Updated dependencies [a0a02f4]
+- Updated dependencies [0aed425]
+- Updated dependencies [eaf030b]
+- Updated dependencies [7de0397]
+- Updated dependencies [674c658]
+- Updated dependencies [de27557]
+- Updated dependencies [2173644]
+- Updated dependencies [4d894b0]
+- Updated dependencies [61901cd]
+- Updated dependencies [5e366e2]
+- Updated dependencies [2938a0d]
+- Updated dependencies [dc8439c]
+- Updated dependencies [b19cb37]
+- Updated dependencies [4330e40]
+- Updated dependencies [4199ff3]
+- Updated dependencies [90d9ee6]
+- Updated dependencies [364a234]
+- Updated dependencies [c06cba5]
+- Updated dependencies [f4d3852]
+- Updated dependencies [4a82ae0]
+- Updated dependencies [0ff867a]
+- Updated dependencies [e7391bf]
+- Updated dependencies [0b80a59]
+- Updated dependencies [c64db12]
+- Updated dependencies [3753104]
+- Updated dependencies [4b3b1fa]
+- Updated dependencies [3562557]
+- Updated dependencies [53087f3]
+- Updated dependencies [2def6c7]
+- Updated dependencies [b5b5bc3]
+- Updated dependencies [22e1777]
+- Updated dependencies [3a483cd]
+- Updated dependencies [35f52c7]
+- Updated dependencies [343cb81]
+- Updated dependencies [412a9ee]
+- Updated dependencies [65883e5]
+- Updated dependencies [0e20529]
+- Updated dependencies [d91fd44]
+- Updated dependencies [f7e36ec]
+- Updated dependencies [262e46d]
+- Updated dependencies [b13e071]
+- Updated dependencies [944623d]
+- Updated dependencies [6d9869d]
+- Updated dependencies [077657f]
+- Updated dependencies [b9cc68c]
+- Updated dependencies [de2cc1d]
+- Updated dependencies [a5963cb]
+- Updated dependencies [05aac0e]
+- Updated dependencies [1a6616f]
+- Updated dependencies [ecd738e]
+- Updated dependencies [7775c2b]
+- Updated dependencies [05587e0]
+- Updated dependencies [c75818d]
+- Updated dependencies [3db36b3]
+- Updated dependencies [7775c2b]
+- Updated dependencies [09c47c5]
+- Updated dependencies [326caee]
+- Updated dependencies [f8e0ed5]
+- Updated dependencies [a588c18]
+- Updated dependencies [1cdcfe5]
+- Updated dependencies [e195fe8]
+- Updated dependencies [846e2f6]
+- Updated dependencies [55f4fdb]
+- Updated dependencies [7775c2b]
+- Updated dependencies [d3e79c4]
+- Updated dependencies [d922f65]
+- Updated dependencies [aadd9fc]
+- Updated dependencies [ea16748]
+- Updated dependencies [a1eda0a]
+- Updated dependencies [fc0284a]
+- Updated dependencies [5b22f4d]
+- Updated dependencies [1b94593]
+- Updated dependencies [9f58295]
+- Updated dependencies [2f7299a]
+- Updated dependencies [29e62a0]
+- Updated dependencies [c613e7d]
+- Updated dependencies [5975163]
+- Updated dependencies [b9608ac]
+- Updated dependencies [7a165de]
+- Updated dependencies [4064f36]
+- Updated dependencies [d8f11a5]
+- Updated dependencies [e9e02cf]
+- Updated dependencies [b70b18a]
+- Updated dependencies [6f42b38]
+- Updated dependencies [870227d]
+- Updated dependencies [48aad8c]
+- Updated dependencies [2fbb4f0]
+- Updated dependencies [1d66252]
+- Updated dependencies [a6a6834]
+- Updated dependencies [166a6ff]
+- Updated dependencies [79be5af]
+- Updated dependencies [41050ed]
+- Updated dependencies [fc837cb]
+- Updated dependencies [bf6eeb0]
+- Updated dependencies [5a3c27a]
+- Updated dependencies [15a3a66]
+- Updated dependencies [b80ce77]
+- Updated dependencies [9b971fc]
+- Updated dependencies [2577fc7]
+- Updated dependencies [9b1acc9]
+- Updated dependencies [391ab3c]
+- Updated dependencies [3bf7d6b]
+- Updated dependencies [7775c2b]
+- Updated dependencies [ab1935b]
+- Updated dependencies [740109f]
+- Updated dependencies [e0a25fe]
+- Updated dependencies [3630b6e]
+- Updated dependencies [1290c6d]
+- Updated dependencies [d0a7d58]
+  - @nifrajs/web@5.0.0
+  - @nifrajs/core@5.0.0
+  - @nifrajs/i18n@5.0.0
+  - @nifrajs/image@5.0.0
+
+## 4.0.2
+
+### Patch Changes
+
+- Updated dependencies [fcd6a5b]
+  - @nifrajs/web@4.0.2
+  - @nifrajs/core@4.0.2
+  - @nifrajs/i18n@4.0.2
+  - @nifrajs/image@4.0.2
+
+## 4.0.1
+
+### Patch Changes
+
+- Updated dependencies [bbb2b27]
+- Updated dependencies [2957acd]
+- Updated dependencies [4bd292a]
+- Updated dependencies [55e813b]
+  - @nifrajs/web@4.0.1
+  - @nifrajs/core@4.0.1
+  - @nifrajs/i18n@4.0.1
+  - @nifrajs/image@4.0.1
+
+## 4.0.0
+
+### Major Changes
+
+- a8b33bc: The Solid and Svelte compiler plugins live on their `/plugin` subpaths, and each adapter root exports only the render adapter.
+
+  - `solidBunPlugin` is imported from `@nifrajs/web-solid/plugin`, matching `@nifrajs/web-svelte/plugin` and `@nifrajs/web-vue/plugin`.
+  - `@nifrajs/web-solid` and `@nifrajs/web-svelte` link no build-time or `node:` module, so a server or edge bundle that imports the adapter builds under edge resolve conditions (Cloudflare Workers, Vercel Edge, Deno).
+  - Solid site scaffolds import the plugin from the subpath.
+
+  Breaking: `solidBunPlugin` is no longer exported from `@nifrajs/web-solid`, nor `svelteBunPlugin` from `@nifrajs/web-svelte`. `nifra fix --code NF-C005` rewrites those imports.
+
+### Minor Changes
+
+- f70f99b: feat(i18n): selectordinal, fallback catalogs, typed nested catalogs and the locale cookie
+
+  The formatter supports `selectordinal` (`{n, selectordinal, one {#st} two {#nd} few {#rd} other {#th}}`).
+  Inside a `plural` or `selectordinal` case, `#` is now the number in the locale's own format
+  (`1,000 items`, `1.000 Artikel`) instead of its plain digits - the output changes for counts of 1,000
+  and more and for fractions.
+
+  `createFormatter(locale, messages, options)` takes `fallback` catalogs, tried in order for a key the
+  catalog lacks (`locales.chain()` gives the order); `onMissing(key, locale)`, called once per key when
+  no catalog has it; and `timeZone` and `numberingSystem` defaults for `d()`, `n()` and `#`. An invalid
+  locale, time zone or numbering system throws at creation. Formatters are cached per catalog and
+  options, with bounded caches, so per-request values cannot grow memory.
+
+  Catalogs may nest: values are messages, lists or blocks, read with dotted keys (`t("home.title")`); a
+  flat key that contains a dot is found first, so flat catalogs work unchanged. `get(key)` returns a list
+  or block whole. Lookups read own properties only, and an argument named like an `Object.prototype`
+  member renders empty unless passed. Declaring `interface Register { messages: typeof en }` on
+  `@nifrajs/i18n` types every `t()` and `get()` key, and other locales' catalogs (`Translation`,
+  `PartialMessages`) against that shape.
+
+  `localeCookie(name, locale, { maxAge })` returns the `document.cookie` string for a language switcher,
+  byte-identical to the `Set-Cookie` `localeDetector({ persist: true })` writes.
+
+  Every adapter's `<I18nProvider>` takes `fallback`, `onMissing`, `timeZone` and `numberingSystem`, and
+  its `messages` prop is checked against the registered catalog type.
+
+- 49f106f: feat(i18n): rich text from catalog messages without HTML
+
+  `rich(formatter, key, tags, vars)` from the new `@nifrajs/i18n/rich` entry formats a message like
+  `t()` and turns its `<name>…</name>` and `<name/>` tags into calls to `tags[name]`, returning the
+  message as text and whatever the handlers returned. Tags are bare names (no attributes); a tag
+  without an own handler keeps its content as text, an unclosed or stray marker stays literal, and
+  interpolated values and `#` are never read for tags. `renderRich(renderer, ...)` is the same for a
+  UI framework.
+
+  React, Preact, Solid and Vue export `rich(t, key, tags, vars)` from `/i18n`, returning one node
+  (each handler receives its tag's content as one node, and `<br/>` renders a `<br>` unless `br` is
+  given). Svelte exports `<Rich key tags vars>`, which takes one snippet per tag, and `rich()` for the
+  parts array. `t()` is unchanged.
+
+- 0f6babe: feat(web): a route can export a `handle`, and `useMatches()` reports the rendered chain on every adapter.
+
+  ```tsx
+  // routes/orgs/[org]/_layout.tsx
+  import { useMatches } from "@nifrajs/web-react/router";
+
+  export const handle = { crumb: "Organization" };
+
+  export default function OrgLayout({
+    children,
+  }: {
+    children: React.ReactNode;
+  }) {
+    const crumbs = useMatches().flatMap(
+      (m) => (m.handle as { crumb?: string } | undefined)?.crumb ?? []
+    );
+    // ...
+  }
+  ```
+
+  `useMatches()` lists the layouts being rendered, outermost first, then the page, each as
+  `{ id, pathname, params, data, handle }`: the route file without its extension, the part of the URL
+  it covers (never the query), the params it declares, its loader data (`null` without a loader), and
+  its `handle` export. The server render and the browser report the same list, so a breadcrumb trail
+  hydrates with no mismatch. `handle` is read from the module on each side and never serialized.
+
+  While a `_loading` page is up it takes the page's place; a nested `_404` reports the layouts it
+  renders inside; an `_error` page the server renders reports an empty list. The hook ships from each
+  adapter's `/router` entry: an array on React and Preact, a `Ref` on Vue, an accessor on Solid and
+  Svelte. An app that never calls it does not bundle it.
+
+  The Preact, Solid, Vue and Svelte client mounts now pass `params` and `path` to the rendered chain,
+  as the server render already did. `UIMatch` and `MatchChain` are exported from `@nifrajs/web`.
+
+### Patch Changes
+
+- ee19d29: fix(web-react, web-preact, web-vue, web-solid, web-svelte): a layout keeps its loader data in the
+  browser. The mounted router rendered every layout with `data: null` - on the first paint, where the
+  server had rendered the layout with its data and the client render no longer matched it, and after
+  each client navigation. It now hands each layout the data the router holds for it. On Solid a layout
+  also follows a same-route update, so new layout data after a revalidation or a param change arrives
+  without the layout remounting.
+- 6393b1e: feat(web): `_loading.tsx` is what the page slot shows while a client navigation loads. A navigation
+  still waiting on its data after about 120 ms swaps the page for the target route's nearest
+  `_loading` - the innermost one above it whose layouts are already on screen, which are the layouts
+  the two pages share; they stay mounted with their data. A `_loading` never renders outside a layout
+  above it. A navigation that settles sooner goes straight to the new page, as does one with no
+  eligible `_loading`; a change of search on the same path and a form submit keep the page. A newer
+  navigation, a form submit, or a refresh of the page on screen takes over from a pending loading
+  page, and a superseded navigation that fails later changes nothing. The
+  component receives `pending` and no `data`. It is browser-only: the server never renders one, and an
+  app without a `_loading` file ships no code for it. Where the browser runs view transitions, a
+  navigation's transition ends on the loading page instead of holding the old page until the data
+  arrives. `Manifest.loadings` lists the pages (`LoadingEntry`, each with the layouts it sits under)
+  and `RouteEntry.loadingIds` the ones above each route. In a `buildClient` build every page links the
+  loading pages' stylesheets.
+
+  A file named `_loading` was an ignored underscore file before; one kept in a routes directory for
+  another purpose is now a loading page.
+
+  fix(web-solid): the mounted router renders the chain the router names while a navigation is pending,
+  which is how a `_loading` page reaches the screen. A pending navigation on the same chain is still
+  skipped until it settles.
+
+- 1ae5543: The MDX runtime's intrinsic components always render their own tag: a `component` prop on a Markdown element no longer replaces the element, and the element's props stay reactive. `useMDXComponents()` now types each component's result as `JSX.Element` instead of `unknown`.
+- 64e7a42: fix(web): pages that `defer()` keep working under a nonce Content-Security-Policy.
+  React, Solid and Preact stream inline scripts to reveal a Suspense boundary that resolves after the
+  shell, and none of them carried the document's nonce, so a nonce CSP blocked them and the boundary
+  stayed on its fallback. `RenderAdapter.renderToStream` now receives `{ nonce }` as an optional third
+  argument (`RenderStreamOptions`), and every adapter that streams scripts applies it: React and Solid
+  through their own `nonce` option, Preact on the one island-runtime script it streams. A script the
+  app renders itself never inherits the nonce. Vue, Svelte and the vanilla adapter stream no scripts.
+- Updated dependencies [dde125b]
+- Updated dependencies [22e2af8]
+- Updated dependencies [72b62fa]
+- Updated dependencies [aa44e93]
+- Updated dependencies [4a3ee60]
+- Updated dependencies [963694f]
+- Updated dependencies [aad6297]
+- Updated dependencies [dad0d41]
+- Updated dependencies [538adc2]
+- Updated dependencies [f47edd1]
+- Updated dependencies [df9530a]
+- Updated dependencies [3e6973f]
+- Updated dependencies [25e8edf]
+- Updated dependencies [2b5e5fc]
+- Updated dependencies [3b090de]
+- Updated dependencies [da7d792]
+- Updated dependencies [612a296]
+- Updated dependencies [fb14dfa]
+- Updated dependencies [8ae97f6]
+- Updated dependencies [4af6f39]
+- Updated dependencies [ca8b50d]
+- Updated dependencies [b00a889]
+- Updated dependencies [b53d64f]
+- Updated dependencies [66fd712]
+- Updated dependencies [9c3d524]
+- Updated dependencies [738e7a1]
+- Updated dependencies [4801cac]
+- Updated dependencies [1b2d53a]
+- Updated dependencies [25fe13d]
+- Updated dependencies [0852290]
+- Updated dependencies [0589dbe]
+- Updated dependencies [2e2d8c0]
+- Updated dependencies [856f5ce]
+- Updated dependencies [18aa5aa]
+- Updated dependencies [cfd86b3]
+- Updated dependencies [8ff96c9]
+- Updated dependencies [4c46199]
+- Updated dependencies [eef4932]
+- Updated dependencies [6de8686]
+- Updated dependencies [86e2d0f]
+- Updated dependencies [a0cfffa]
+- Updated dependencies [d7892ea]
+- Updated dependencies [93e5e7f]
+- Updated dependencies [214d674]
+- Updated dependencies [4936309]
+- Updated dependencies [ff5a779]
+- Updated dependencies [772249a]
+- Updated dependencies [f70f99b]
+- Updated dependencies [49f106f]
+- Updated dependencies [4936309]
+- Updated dependencies [def0172]
+- Updated dependencies [fc2f019]
+- Updated dependencies [a734fba]
+- Updated dependencies [0e9b167]
+- Updated dependencies [bbdc5a1]
+- Updated dependencies [10bc446]
+- Updated dependencies [e8270d9]
+- Updated dependencies [d942c33]
+- Updated dependencies [ef28ef9]
+- Updated dependencies [ff4a062]
+- Updated dependencies [43ba944]
+- Updated dependencies [46c741a]
+- Updated dependencies [7bfa25e]
+- Updated dependencies [216fe27]
+- Updated dependencies [4936309]
+- Updated dependencies [6e257a6]
+- Updated dependencies [4a03d30]
+- Updated dependencies [8e30090]
+- Updated dependencies [28f3aaf]
+- Updated dependencies [6d20355]
+- Updated dependencies [08250bf]
+- Updated dependencies [6907cbe]
+- Updated dependencies [4b8d8de]
+- Updated dependencies [ba5dd1c]
+- Updated dependencies [d50f73e]
+- Updated dependencies [031c33d]
+- Updated dependencies [8fa902c]
+- Updated dependencies [085e852]
+- Updated dependencies [0dac7ec]
+- Updated dependencies [b64c3ee]
+- Updated dependencies [dc2d4d3]
+- Updated dependencies [bda9637]
+- Updated dependencies [81c720e]
+- Updated dependencies [ed60b23]
+- Updated dependencies [0150ed4]
+- Updated dependencies [ae815ab]
+- Updated dependencies [ea2ee87]
+- Updated dependencies [3442e1c]
+- Updated dependencies [85d636b]
+- Updated dependencies [6c978a1]
+- Updated dependencies [bfe29b6]
+- Updated dependencies [8b99424]
+- Updated dependencies [87783f0]
+- Updated dependencies [135aba4]
+- Updated dependencies [47b0d65]
+- Updated dependencies [e32268d]
+- Updated dependencies [432fec3]
+- Updated dependencies [0e14068]
+- Updated dependencies [8f1b780]
+- Updated dependencies [dcc9ff6]
+- Updated dependencies [5a63dd4]
+- Updated dependencies [c49882f]
+- Updated dependencies [dfd19d8]
+- Updated dependencies [28e091f]
+- Updated dependencies [046e79d]
+- Updated dependencies [6393b1e]
+- Updated dependencies [a158b74]
+- Updated dependencies [ee19d29]
+- Updated dependencies [293d3c8]
+- Updated dependencies [7e1e1c3]
+- Updated dependencies [0cd5f6e]
+- Updated dependencies [2245bee]
+- Updated dependencies [feeec4a]
+- Updated dependencies [3eb6339]
+- Updated dependencies [f784c32]
+- Updated dependencies [e3b2b97]
+- Updated dependencies [5934b5d]
+- Updated dependencies [03a3729]
+- Updated dependencies [bd11269]
+- Updated dependencies [579d9a9]
+- Updated dependencies [3554ad8]
+- Updated dependencies [64e7a42]
+- Updated dependencies [ee19d29]
+- Updated dependencies [d6f806f]
+- Updated dependencies [38cf032]
+- Updated dependencies [b94e5cb]
+- Updated dependencies [0f6babe]
+- Updated dependencies [00f18bf]
+- Updated dependencies [a84f546]
+- Updated dependencies [669b6a2]
+- Updated dependencies [ff25d68]
+  - @nifrajs/core@4.0.0
+  - @nifrajs/web@4.0.0
+  - @nifrajs/i18n@4.0.0
+  - @nifrajs/image@4.0.0
+
+## 3.5.0
+
+### Patch Changes
+
+- Updated dependencies [6046984]
+- Updated dependencies [ac27343]
+- Updated dependencies [d5b7c22]
+  - @nifrajs/core@3.5.0
+  - @nifrajs/web@3.5.0
+  - @nifrajs/image@3.5.0
+  - @nifrajs/i18n@3.5.0
+
+## 3.4.0
+
+### Patch Changes
+
+- 8d23613: Add the opt-in `@nifrajs/webmcp` package: typed WebMCP registration, core-backed receipts, deterministic predictive-UI reconciliation, and host-independent conformance checks. Also tighten agent execution cancellation cleanup so aborted local work cannot leak into later turns.
+- Updated dependencies [8d23613]
+- Updated dependencies [8d23613]
+- Updated dependencies
+- Updated dependencies [719d82e]
+  - @nifrajs/web@3.4.0
+  - @nifrajs/core@3.4.0
+  - @nifrajs/i18n@3.4.0
+  - @nifrajs/image@3.4.0
+
+## 3.3.0
+
+### Patch Changes
+
+- @nifrajs/core@3.3.0
+- @nifrajs/i18n@3.3.0
+- @nifrajs/image@3.3.0
+- @nifrajs/web@3.3.0
+
+## 3.2.0
+
+### Patch Changes
+
+- c39712e: Move route policy compilation and deploy-target planning behind shared internal seams, pin the Solid adapter's Babel type identity, and add a cleanup-safe cross-runtime contract-lab runner.
+- Updated dependencies [652201a]
+- Updated dependencies [3aefb12]
+- Updated dependencies [8b58d1f]
+- Updated dependencies [c4ed8f7]
+- Updated dependencies [25305bb]
+- Updated dependencies [095c320]
+- Updated dependencies [7504864]
+- Updated dependencies [e88c23a]
+- Updated dependencies [c39712e]
+- Updated dependencies [9010fd3]
+- Updated dependencies [7551709]
+- Updated dependencies [ea2356e]
+- Updated dependencies [a816b87]
+  - @nifrajs/web@3.2.0
+  - @nifrajs/core@3.2.0
+  - @nifrajs/image@3.2.0
+  - @nifrajs/i18n@3.2.0
+
+## 3.1.0
+
+### Patch Changes
+
+- 8b136ee: Framework bindings now share consistent query and fetcher idle behavior while keeping mounted-router state isolated per adapter.
+- Updated dependencies [5b78473]
+- Updated dependencies [1400f6c]
+- Updated dependencies [8b136ee]
+- Updated dependencies [a7db515]
+  - @nifrajs/core@3.1.0
+  - @nifrajs/i18n@3.1.0
+  - @nifrajs/web@3.1.0
+  - @nifrajs/image@3.1.0
+
+## 3.0.0
+
+### Patch Changes
+
+- 86a555b: The roadmap contract surfaces are now shipped across the public packages: shared island triggers,
+  typed content indexes and joins, client loader/action hooks, and unified static, dynamic, and
+  intercepting boundary modes. WebSocket routes also support opt-in synchronous outbound validation
+  through `sendSchema` + `validateSend`; invalid or asynchronous outbound frames fail closed while the
+  default remains type-level only.
+- Updated dependencies [f3d2a35]
+- Updated dependencies [6e43c15]
+- Updated dependencies [293a7fe]
+- Updated dependencies [485ae60]
+- Updated dependencies [627b0ba]
+- Updated dependencies [f0fd370]
+- Updated dependencies [004deee]
+- Updated dependencies [86a555b]
+- Updated dependencies [8c5f4cf]
+- Updated dependencies [f0fd370]
+- Updated dependencies [381bbf3]
+- Updated dependencies [36801ae]
+- Updated dependencies [9acadba]
+- Updated dependencies [99fc683]
+- Updated dependencies [73d894d]
+  - @nifrajs/core@3.0.0
+  - @nifrajs/web@3.0.0
+  - @nifrajs/i18n@3.0.0
+  - @nifrajs/image@3.0.0
+
+## 2.14.1
+
+### Patch Changes
+
+- Updated dependencies [bf93902]
+  - @nifrajs/core@2.14.1
+  - @nifrajs/i18n@2.14.1
+  - @nifrajs/web@2.14.1
+  - @nifrajs/image@2.14.1
+
+## 2.14.0
+
+### Patch Changes
+
+- Updated dependencies [489c6b6]
+- Updated dependencies [701961a]
+- Updated dependencies [62e22e2]
+- Updated dependencies [62e22e2]
+- Updated dependencies [62133bf]
+- Updated dependencies [8dffdf4]
+- Updated dependencies [489c6b6]
+  - @nifrajs/web@2.14.0
+  - @nifrajs/core@2.14.0
+  - @nifrajs/i18n@2.14.0
+  - @nifrajs/image@2.14.0
+
+## 2.13.0
+
+### Patch Changes
+
+- Updated dependencies [e0b2dd6]
+- Updated dependencies [7535ce1]
+- Updated dependencies [1704308]
+- Updated dependencies [6510fdc]
+  - @nifrajs/core@2.13.0
+  - @nifrajs/web@2.13.0
+  - @nifrajs/i18n@2.13.0
+  - @nifrajs/image@2.13.0
+
+## 2.12.1
+
+### Patch Changes
+
+- Updated dependencies [fba30c7]
+  - @nifrajs/core@2.12.1
+  - @nifrajs/i18n@2.12.1
+  - @nifrajs/web@2.12.1
+  - @nifrajs/image@2.12.1
+
+## 2.12.0
+
+### Patch Changes
+
+- Updated dependencies [df100d3]
+- Updated dependencies [0efacea]
+- Updated dependencies [cd1732c]
+- Updated dependencies [df100d3]
+- Updated dependencies [9a9346e]
+- Updated dependencies [b5f47c0]
+- Updated dependencies [fc33c0f]
+- Updated dependencies [fa51aba]
+- Updated dependencies [c4e8bb0]
+- Updated dependencies [11d1658]
+- Updated dependencies [33ee9ff]
+- Updated dependencies [ceda72d]
+- Updated dependencies [2c004ca]
+- Updated dependencies [5f71c23]
+- Updated dependencies [3788b36]
+- Updated dependencies [0863ef0]
+- Updated dependencies [ae5338f]
+- Updated dependencies [8847825]
+- Updated dependencies [9a9346e]
+- Updated dependencies [4c2123d]
+- Updated dependencies [5e4e31a]
+- Updated dependencies [24f1787]
+- Updated dependencies [9a9346e]
+- Updated dependencies [b045f9e]
+- Updated dependencies [df07059]
+- Updated dependencies [9a9346e]
+- Updated dependencies [9a9346e]
+- Updated dependencies [dbc0b79]
+- Updated dependencies [bd5c624]
+- Updated dependencies [a5d3f5b]
+- Updated dependencies [00819c5]
+- Updated dependencies [e2bdd4a]
+- Updated dependencies [e2d1939]
+- Updated dependencies [e83e6eb]
+- Updated dependencies [64d25db]
+- Updated dependencies [c55f7a3]
+- Updated dependencies [f8b0097]
+  - @nifrajs/core@2.12.0
+  - @nifrajs/i18n@2.12.0
+  - @nifrajs/web@2.12.0
+  - @nifrajs/image@2.12.0
+
+## 2.11.0
+
+### Minor Changes
+
+- ed5e91c: Vue, Solid and Svelte hot-patch a component edit in place on the Bun dev pipeline: the page keeps its scroll position, its open dialogs and the rest of its client state, and only the edited component re-renders. Route modules still full-reload on save, since a route carries the loader and meta the server ran. The wiring is emitted for a dev server's client compile only, so nothing reaches a production bundle.
+
+  `@nifrajs/web-svelte/plugin` adds `svelteHmrBoundary`, the same boundary for the Vite pipeline - pass it to `@sveltejs/vite-plugin-svelte` as `dynamicCompileOptions`. Svelte's hot-patch wrapper resolves a component through a signal, which reconciles against server markup only where the component is a plain child in a template; a layout or a page is neither, and wrapping one desyncs hydration on first load. The boundary keeps the wrapper on the app's own views. (Svelte recreates the patched component, so its own `$state` restarts - Vue and Solid preserve theirs.)
+
+  `Router.svelte` now takes `searchOfChain` from `@nifrajs/web/client` rather than the package root, so a client bundle no longer reaches server-only modules through it.
+
+### Patch Changes
+
+- 30f5ea3: SSR renders the code that is on disk on the Bun dev pipeline, not just for route files. An edit to anything a route imports - a component, a helper, a `*.server` module, at any depth - now reaches the server-rendered HTML on the next request, so a saved change no longer shows up on the client while the SSR pass still renders the version the server started with. All four frameworks, and both `import "./Counter"` and `import "./Counter.tsx"`.
+
+  A module nobody edited keeps its identity, so a database client or any other module-scope singleton shared between the backend and a route is still a single instance; editing that module deliberately gives the routes the new code. The Vite pipeline is unchanged - it already owned an SSR module graph.
+
+  `@nifrajs/web/plugins/kit` adds `rewriteSsrImports`, which a plugin that compiles its own file type passes its `generate: "ssr"` output through - the compiling plugin is the only code that sees that file's imports, so it is the only place they can be re-keyed.
+
+- Updated dependencies [ed5e91c]
+- Updated dependencies [30f5ea3]
+- Updated dependencies [c29e0d0]
+  - @nifrajs/web@2.11.0
+  - @nifrajs/core@2.11.0
+  - @nifrajs/i18n@2.11.0
+  - @nifrajs/image@2.11.0
+
+## 2.10.0
+
+### Patch Changes
+
+- Updated dependencies [5263c4e]
+- Updated dependencies [15bffdd]
+- Updated dependencies [15bffdd]
+- Updated dependencies [15bffdd]
+  - @nifrajs/web@2.10.0
+  - @nifrajs/core@2.10.0
+  - @nifrajs/image@2.10.0
+  - @nifrajs/i18n@2.10.0
+
+## 2.9.1
+
+### Patch Changes
+
+- Updated dependencies [01e36fb]
+  - @nifrajs/core@2.9.1
+  - @nifrajs/web@2.9.1
+  - @nifrajs/i18n@2.9.1
+  - @nifrajs/image@2.9.1
+
+## 2.9.0
+
+### Patch Changes
+
+- Updated dependencies [e05e56d]
+  - @nifrajs/core@2.9.0
+  - @nifrajs/web@2.9.0
+  - @nifrajs/i18n@2.9.0
+  - @nifrajs/image@2.9.0
+
+## 2.8.2
+
+### Patch Changes
+
+- Updated dependencies [f7d68e8]
+  - @nifrajs/core@2.8.2
+  - @nifrajs/image@2.8.2
+  - @nifrajs/web@2.8.2
+  - @nifrajs/i18n@2.8.2
+
+## 2.8.1
+
+### Patch Changes
+
+- Updated dependencies [78d66a4]
+- Updated dependencies [93fdc89]
+  - @nifrajs/core@2.8.1
+  - @nifrajs/web@2.8.1
+  - @nifrajs/i18n@2.8.1
+  - @nifrajs/image@2.8.1
+
+## 2.8.0
+
+### Patch Changes
+
+- Updated dependencies [118e4a5]
+  - @nifrajs/web@2.8.0
+  - @nifrajs/core@2.8.0
+  - @nifrajs/i18n@2.8.0
+  - @nifrajs/image@2.8.0
+
+## 2.7.1
+
+### Patch Changes
+
+- Updated dependencies [52c89e0]
+  - @nifrajs/core@2.7.1
+  - @nifrajs/web@2.7.1
+  - @nifrajs/i18n@2.7.1
+  - @nifrajs/image@2.7.1
+
+## 2.7.0
+
+### Patch Changes
+
+- @nifrajs/core@2.7.0
+- @nifrajs/i18n@2.7.0
+- @nifrajs/image@2.7.0
+- @nifrajs/web@2.7.0
+
+## 2.6.1
+
+### Patch Changes
+
+- Updated dependencies [5840c98]
+- Updated dependencies [80419f5]
+  - @nifrajs/core@2.6.1
+  - @nifrajs/web@2.6.1
+  - @nifrajs/i18n@2.6.1
+  - @nifrajs/image@2.6.1
+
+## 2.6.0
+
+### Patch Changes
+
+- Updated dependencies [e6349e5]
+- Updated dependencies [08fe221]
+- Updated dependencies [8383063]
+  - @nifrajs/web@2.6.0
+  - @nifrajs/core@2.6.0
+  - @nifrajs/i18n@2.6.0
+  - @nifrajs/image@2.6.0
+
+## 2.5.0
+
+### Patch Changes
+
+- 02d9aa8: Routing hooks now SSR-render correctly on the dev server. In dev, the adapter is imported by Bun while route modules load through Vite's SSR runner, so the router module could be evaluated twice in one process - two context objects, and `useSearch`/`useParams`/`useLocation` read a context the render never provided. The result was hooks SSR-rendering their empty defaults (`useSearch()` gave `{}`) while the same request's loader saw the validated values; hydration then papered over it on the client, so it surfaced as "the search schema doesn't work in dev". The router context in every adapter is now a `globalThis` singleton (keyed by `Symbol.for`), so both evaluations share the one context React/Vue/Solid/Preact matches providers to readers by. The Vite dev server also mirrors its client `resolve.conditions` into `ssr.resolve.{conditions,externalConditions}`, so dev SSR resolves the same `bun`-conditioned source files Bun does instead of a package's `dist` artifact - which nothing in the dev loop rebuilds, and whose staleness previously 500'd inside framework code.
+- Updated dependencies [02d9aa8]
+  - @nifrajs/web@2.5.0
+  - @nifrajs/core@2.5.0
+  - @nifrajs/i18n@2.5.0
+  - @nifrajs/image@2.5.0
+
+## 2.4.0
+
+### Patch Changes
+
+- Updated dependencies [1c2bf5a]
+- Updated dependencies [138bfba]
+- Updated dependencies [23e6eb1]
+  - @nifrajs/web@2.4.0
+  - @nifrajs/core@2.4.0
+  - @nifrajs/i18n@2.4.0
+  - @nifrajs/image@2.4.0
+
+## 2.3.0
+
+### Minor Changes
+
+- 2d9beaa: Preact, Vue, Solid and Svelte gain `useNavigate` and `useBlocker`, from `@nifrajs/web-<framework>/router`.
+
+  `useNavigate` returns a programmatic navigate (a path pushes or replaces; a number is a history delta),
+  matching the React adapter. `useBlocker` is the unsaved-changes guard - pass a boolean or a
+  `({ currentLocation, nextLocation }) => boolean` predicate and get back a `{ state, proceed, reset }`
+  value in each framework's own reactive shape (a Vue ref, a Solid accessor, a Svelte store, a plain value
+  in Preact). When a navigation is intercepted, `state` becomes `"blocked"`; show your own confirmation and
+  call `proceed()` or `reset()`. It also arms the native "Leave site?" prompt on tab close and reload.
+
+  ```svelte
+  <script>
+    import { useBlocker } from "@nifrajs/web-svelte/router"
+    let dirty = false
+    const blocker = useBlocker(() => dirty)
+  </script>
+
+  {#if $blocker.state === "blocked"}
+    <dialog open>
+      <button on:click={$blocker.reset}>Keep editing</button>
+      <button on:click={$blocker.proceed}>Discard</button>
+    </dialog>
+  {/if}
+  ```
+
+  In Vue, Solid and Svelte the hook is created once, so pass a function to track a changing flag
+  (`useBlocker(() => dirty)`); a bare boolean is captured as-is. The guarding itself already ran on every
+  adapter at the browser layer - this exposes it as a reactive hook.
+
+- c823915: Typed, validated search params: a route declares a `searchSchema` and both its loader and its component read the parsed, validated query.
+
+  Export a Standard Schema as `searchSchema` from a route. The loader's `ctx.search` becomes the parsed URL query validated against it (typed via `LoaderArgs<typeof app, Env, typeof searchSchema>`), and the component reads the same value with `useSearch<typeof searchSchema>()`. Invalid or hostile input fails closed to the schema's defaults (never a 500); without a `searchSchema`, both are the raw parsed query. Validation runs at match time and the value is derived identically on the server and on client navigation, so a component never parses `window.location.search` by hand and the query it renders hydrates with no mismatch.
+
+  ```tsx
+  export const searchSchema = v.object({
+    page: v.optional(v.fallback(v.number(), 1), 1),
+  });
+
+  export async function loader({
+    search,
+    api,
+  }: LoaderArgs<typeof backend, unknown, typeof searchSchema>) {
+    return { rows: await api.reports.list(search).get() }; // search.page is a number
+  }
+
+  export default function Reports({ data }) {
+    const { page } = useSearch<typeof searchSchema>(); // page: number, SSR-correct
+    return <Pager page={page} />;
+  }
+  ```
+
+  A `_layout` can declare its own `searchSchema` for keys shared across a section (`?org`, `?theme`); the route's effective search merges the layout chain's schemas with the page's, page-wins on a conflict, so both the layout and the page read their validated slice from one object.
+
+  A route can also list `searchClientKeys` - search keys that are purely client-side UI (`?tab`, a client-side `?sort`, `?modal`). When a client navigation changes only those keys, the URL updates (so `useSearch` re-renders) without re-running the loader; any other key change revalidates as before, so data is never stale.
+
+  `useSearch` ships on every adapter - React (a value), Preact (a value), Vue (a `Ref`), Solid (an `Accessor`), and Svelte (an accessor), each in that framework's own shape.
+
+  `navigate` gains an object form on every adapter: `navigate({ to, search, replace })` serializes `search` onto `to` (no hand-built query strings). Run `nifra sync-routes` to generate `nifra-routes.d.ts` (each static route mapped to its schema output) and include it in your tsconfig, and `search` is typed against the target route's `searchSchema` - a wrong shape for a known route is a compile error, while an unmapped path takes a loose `search`. Regenerated from the route files, so a stale shape becomes a `tsc` error. The string-path and history-delta forms are unchanged.
+
+  ```ts
+  navigate({ to: "/reports", search: { page: 2 } }); // search typed against /reports's schema
+  ```
+
+- 62a8d03: Add `useServerFn` - a server function's pending, data and error state - to all five adapters.
+
+  ```tsx
+  const addTodo = useServerFn(fns.addTodo)
+  <button disabled={addTodo.pending} onClick={() => addTodo.call({ text }).catch(() => {})}>add</button>
+  ```
+
+  Calling a server function never needed a binding: the client stub is `(input) => Promise<Output>`.
+  This adds only the state a component wants around it.
+
+  The state machine is `@nifrajs/web`'s `createServerFnStore`, shared by every adapter, so "is it
+  pending" has one answer rather than five that drift. Each binding contributes just its subscription
+  primitive: `useSyncExternalStore` (React, Preact), a signal (Solid), a `shallowRef` (Vue), a `readable`
+  (Svelte).
+
+  Two behaviours worth knowing:
+
+  - **The last call wins.** A response that is no longer the newest is discarded rather than written, so
+    a slow first call landing after a fast second cannot overwrite fresh data with stale.
+  - **`call` still rejects.** The error is recorded for rendering AND the promise rejects, so `await`
+    behaves normally. A caller that only renders from state should attach `.catch(() => {})`, as with
+    `useFetcher`'s `submit`.
+
+  `data` is kept while the next call is in flight, so a rendered list does not blank on every refetch.
+
+### Patch Changes
+
+- fd04bb5: Solid's and Vue's `useServerFn` seed their reactive state from the store rather than from the idle
+  constant.
+
+  Both values are identical today - the store is created one line above and cannot have moved - so this
+  changes no behaviour. It removes the dependence on that staying true. Svelte's binding had the same
+  line reading the constant, and because its subscription is lazy the first render showed idle for a
+  call that had already finished. Reading the snapshot makes correctness independent of when the
+  subscription attaches.
+
+- ea0a27f: A server function has one type per half, so both the server call and the hook argument are honest.
+
+  ```ts
+  export type ClientServerFn<Input, Output> = (
+    input: Input
+  ) => MaybePromise<Output>;
+  export type ServerFnReference<Input, Output> =
+    | ServerFn<Input, Output>
+    | ClientServerFn<Input, Output>;
+  ```
+
+  One type could not describe both halves. `ServerFn` is the SERVER declaration and takes `(input,
+context)`; the client imports a generated stub that takes one argument. Widening the single type so a
+  one-argument call compiled made a direct server call type-check while handing the declaration
+  `undefined` for a context its implementation requires - a runtime failure the compiler had just been
+  told to allow.
+
+  Now the two are separate and `useServerFn` accepts either through `ServerFnReference`, which is the
+  one place the two halves legitimately meet. Calling a declaration from your own server code needs the
+  context, and omitting it is a compile error again.
+
+- Updated dependencies [6f5b3ad]
+- Updated dependencies [85b354d]
+- Updated dependencies [7293a1c]
+- Updated dependencies [8514caa]
+- Updated dependencies [ea0a27f]
+- Updated dependencies [ea0a27f]
+- Updated dependencies [45b0733]
+- Updated dependencies [c42d777]
+- Updated dependencies [ea0a27f]
+- Updated dependencies [b271164]
+- Updated dependencies [8c77d47]
+- Updated dependencies [ea0a27f]
+- Updated dependencies [ea0a27f]
+- Updated dependencies [d190b1c]
+- Updated dependencies [a4ecca9]
+- Updated dependencies [de8d992]
+- Updated dependencies [a92104e]
+- Updated dependencies [5fe332a]
+- Updated dependencies [c823915]
+- Updated dependencies [d2840ac]
+- Updated dependencies [62a8d03]
+- Updated dependencies [dcacfe7]
+- Updated dependencies [28704d7]
+- Updated dependencies [ea0a27f]
+- Updated dependencies [0c2de22]
+  - @nifrajs/core@2.3.0
+  - @nifrajs/web@2.3.0
+  - @nifrajs/i18n@2.3.0
+  - @nifrajs/image@2.3.0
+
+## 2.2.0
+
+### Minor Changes
+
+- 1394641: Layout loaders: request data in the component that wraps every page.
+
+  `routes/_layout.tsx` rendered, but a `loader` it exported never ran, so nothing request-derived could
+  reach a layout - host, session, locale, feature flags, tenant. An app hit this and moved its host guard
+  out of the component tree into the server entry, where it could not be typechecked with the rest of the
+  app. That is the real cost: the gap pushed security-relevant code to the one place nifra's typed-boundary
+  promise does not reach. Remix, React Router and SvelteKit all support this; nifra was alone in not.
+
+  ```tsx
+  // routes/orgs/[org]/_layout.tsx
+  export const gate = true                       // optional; see below
+  export async function loader({ params, req }) {
+    return { org: await findOrg(params.org) }    // params is { org } - nothing deeper
+  }
+  export default function Layout({ data, children }) { … }
+  ```
+
+  **Scoped, not global.** A layout owns the URL prefix it wraps, so it receives only the params inside
+  that prefix and its loader is skipped on a navigation that did not change them. Navigating
+  `/orgs/acme/a` → `/orgs/acme/b` does not re-run the org layout's loader. Scope is derived at build time
+  per `(route, layout)` pair, because one layout can own different params on different expanded patterns:
+  `[[lang]]/docs/_layout` owns nothing on `/docs/:slug` and `{lang}` on `/:lang/docs/:slug`. Layouts are
+  not router nodes and did not become any - the router is untouched.
+
+  **Execution order is declared, and this matters for security.** By default a layout loader runs in
+  parallel with the page's, which is right for data and wrong for a guard: a page loader running
+  concurrently with a guard has already queried by the time the guard says no. `export const gate = true`
+  makes a layout blocking - nothing beneath it runs until it resolves, and nothing beneath a rejected gate
+  runs at all. **A layout loader without `gate: true` is not an authorization boundary.** Gates also run on
+  the data-only request, so a client navigation cannot bypass one by sending the data header, and a gate is
+  never skipped by the retention hint.
+
+  A layout may throw `notFound()` / `gone()` / `redirect()`. Its errors resolve to the `_error` boundary at
+  or above its OWN segment, never one below it - rendering there would wrap the boundary in the very layout
+  whose loader just failed.
+
+  Every adapter passes each layout its own data. A layout with no loader receives `null`, and an app where
+  no layout has a loader emits byte-identical HTML and unchanged props.
+
+  The data-mode response becomes a versioned envelope when a chain carries layout data. It is recognised
+  by structure, and the bare pre-envelope shape is still accepted - a prerendered `_data.json` is a static
+  file that outlives the deploy that wrote it.
+
+### Patch Changes
+
+- Updated dependencies [39b1670]
+- Updated dependencies [d428f52]
+- Updated dependencies [135d0c6]
+- Updated dependencies [1394641]
+- Updated dependencies [e713cab]
+- Updated dependencies [a4645e2]
+- Updated dependencies [a7d740a]
+- Updated dependencies [6e996a1]
+- Updated dependencies [15ad6ca]
+- Updated dependencies [6aa0aac]
+- Updated dependencies [1857d39]
+- Updated dependencies [6ba3173]
+- Updated dependencies [ca71a2e]
+- Updated dependencies [0fc215b]
+- Updated dependencies [2ff661f]
+- Updated dependencies [a1327a4]
+- Updated dependencies [2500705]
+  - @nifrajs/web@2.2.0
+  - @nifrajs/i18n@2.2.0
+  - @nifrajs/image@2.2.0
+
+## 2.1.0
+
+### Patch Changes
+
+- Updated dependencies [bd294bb]
+  - @nifrajs/web@2.1.0
+  - @nifrajs/i18n@2.1.0
+  - @nifrajs/image@2.1.0
+
+## 2.0.0
+
+### Minor Changes
+
+- 3620546: Extend `import Icon from "./icon.svg?component"` to the Solid, Svelte, and Vue adapters (`@nifrajs/web-solid/svg`, `@nifrajs/web-svelte/svg`, `@nifrajs/web-vue/svg`), joining the React/Preact plugin.
+
+  Each is a Bun build plugin that turns a `?component` SVG import into a framework component with the caller's props/attrs spread onto the root `<svg>`, using that framework's own compiler: Solid emits `class`-form JSX through `babel-preset-solid`; Svelte wraps the raw SVG in a Svelte 5 component (compiled by `svelte/compiler`); Vue wraps it in a single-root template so Vue's attribute inheritance forwards props to the `<svg>` (compiled by `@vue/compiler-sfc`). A plain `import "./icon.svg"` asset URL is untouched - only `?component` is intercepted. The shared `svgToJsx` transform gained a `classProp` option.
+
+### Patch Changes
+
+- Updated dependencies [ade0c7a]
+- Updated dependencies [d91a45b]
+- Updated dependencies [d91a45b]
+- Updated dependencies [e97a92f]
+- Updated dependencies [e8e49d1]
+- Updated dependencies [a7d34e5]
+  - @nifrajs/web@2.0.0
+  - @nifrajs/i18n@2.0.0
+  - @nifrajs/image@2.0.0
+
+## 1.13.0
+
+### Patch Changes
+
+- Updated dependencies [5b6127a]
+  - @nifrajs/web@1.13.0
+  - @nifrajs/i18n@1.13.0
+  - @nifrajs/image@1.13.0
+
+## 1.12.0
+
+### Patch Changes
+
+- @nifrajs/web@1.12.0
+- @nifrajs/i18n@1.12.0
+- @nifrajs/image@1.12.0
+
+## 1.11.0
+
+### Patch Changes
+
+- Updated dependencies [5638ada]
+  - @nifrajs/web@1.11.0
+  - @nifrajs/i18n@1.11.0
+  - @nifrajs/image@1.11.0
+
+## 1.10.0
+
+### Patch Changes
+
+- @nifrajs/web@1.10.0
+- @nifrajs/i18n@1.10.0
+- @nifrajs/image@1.10.0
+
+## 1.9.1
+
+### Patch Changes
+
+- Updated dependencies [3eb27ae]
+  - @nifrajs/web@1.9.1
+  - @nifrajs/i18n@1.9.1
+  - @nifrajs/image@1.9.1
+
+## 1.9.0
+
+### Patch Changes
+
+- Updated dependencies [0e1b4cc]
+- Updated dependencies [6b67833]
+  - @nifrajs/web@1.9.0
+  - @nifrajs/i18n@1.9.0
+  - @nifrajs/image@1.9.0
+
+## 1.8.0
+
+### Patch Changes
+
+- Updated dependencies [1ffd48b]
+  - @nifrajs/web@1.8.0
+  - @nifrajs/i18n@1.8.0
+  - @nifrajs/image@1.8.0
+
+## 1.7.0
+
+### Patch Changes
+
+- Updated dependencies [9f23e90]
+  - @nifrajs/web@1.7.0
+  - @nifrajs/i18n@1.7.0
+  - @nifrajs/image@1.7.0
+
+## 1.6.0
+
+### Patch Changes
+
+- @nifrajs/i18n@1.6.0
+- @nifrajs/image@1.6.0
+- @nifrajs/web@1.6.0
+
+## 1.5.0
+
+### Patch Changes
+
+- @nifrajs/web@1.5.0
+- @nifrajs/i18n@1.5.0
+- @nifrajs/image@1.5.0
+
+## 1.4.0
+
+### Patch Changes
+
+- Updated dependencies [4d25970]
+  - @nifrajs/web@1.4.0
+  - @nifrajs/i18n@1.4.0
+  - @nifrajs/image@1.4.0
+
+## 1.3.1
+
+### Patch Changes
+
+- @nifrajs/i18n@1.3.1
+- @nifrajs/image@1.3.1
+- @nifrajs/web@1.3.1
+
+## 1.3.0
+
+### Patch Changes
+
+- Updated dependencies [4a4b1c4]
+  - @nifrajs/web@1.3.0
+  - @nifrajs/i18n@1.3.0
+  - @nifrajs/image@1.3.0
+
+## 1.2.2
+
+### Patch Changes
+
+- @nifrajs/i18n@1.2.2
+- @nifrajs/image@1.2.2
+- @nifrajs/web@1.2.2
+
+## 1.2.1
+
+### Patch Changes
+
+- Updated dependencies [c3ebd73]
+  - @nifrajs/web@1.2.1
+  - @nifrajs/i18n@1.2.1
+  - @nifrajs/image@1.2.1
+
+## 1.2.0
+
+### Patch Changes
+
+- @nifrajs/web@1.2.0
+- @nifrajs/i18n@1.2.0
+- @nifrajs/image@1.2.0
+
+## 1.1.0
+
+### Patch Changes
+
+- Updated dependencies [37d2383]
+  - @nifrajs/web@1.1.0
+  - @nifrajs/i18n@1.1.0
+  - @nifrajs/image@1.1.0
+
+## 1.0.0
+
+### Patch Changes
+
+- Updated dependencies [f1f0e18]
+  - @nifrajs/web@1.0.0
+  - @nifrajs/i18n@1.0.0
+  - @nifrajs/image@1.0.0
+
+## 1.0.0-beta.4
+
+### Patch Changes
+
+- @nifrajs/i18n@1.0.0-beta.4
+- @nifrajs/image@1.0.0-beta.4
+- @nifrajs/web@1.0.0-beta.4
+
+## 1.0.0-beta.3
+
+### Patch Changes
+
+- @nifrajs/i18n@1.0.0-beta.3
+- @nifrajs/image@1.0.0-beta.3
+- @nifrajs/web@1.0.0-beta.3
+
+## 0.1.0-beta.2
+
+### Patch Changes
+
+- Updated dependencies [5018546]
+  - @nifrajs/web@0.1.0-beta.2
+  - @nifrajs/i18n@0.1.0-beta.2
+  - @nifrajs/image@0.1.0-beta.2