Overlapping page and endpoint requests keep their language across awaits. Three initial component fragments load for the active language; a lazy component and another route each bring one more. Same-language routes stay in the document, while language controls start a new one. Catalog failures reach recovery UI before affected components execute.
SvelteKit 3 + Node
The same Svelte messages, from server to browser.
Keep macros in your Svelte components. The SvelteKit integration connects the shared Vite compiler to server rendering, request-local endpoint code, and the browser's catalogs before hydration.
01 — Working example
One booking app. Four languages. Both runtimes.
English, German, French, and Spanish render in the first HTML response, including without JavaScript. Browser checks verify matching hydration, ticket plurals and totals, cart actions, and localized endpoint refreshes in development and production.
02 — Host wiring
One native compiler. A SvelteKit server hook.
The local Vite integration installs Palamedes before SvelteKit. The handle hook creates a runtime per request over a shared compiled server catalog, sets document locale metadata, and installs the active-language browser import map. Components contain no catalog loaders.
The Node adapter bundles the production runtime. A copied build runs without the checkout, PO files, workspace packages, or native compiler. The example uses absolute asset paths through paths: { relative: false }.
03 — Deployment scope
A checked Node integration you can inspect.
The repository example uses SvelteKit 3.1.0, Svelte 5.57.2, Vite 8.2.2, and the Node adapter 6.0.0. It targets a root-mounted, same-origin deployment with query-selected locale and a fixed Europe/Berlin time zone.
The integration is local example code, with no published SvelteKit package. It is separate from the six-family URL-strategy matrix. Other adapters, CDN/subpath assets, prerendering, deferred streaming loads, remote functions, and catalog HMR remain unverified. The integration reference records the compatibility boundary.