Pose una domanda e ottieni un riassunto del documento facendo riferimento a questa pagina e al provider AI di tua scelta
Cronologia delle versioni
- "Init history"v9.0.013/06/2026
Il contenuto di questa pagina è stato tradotto con un'IA.
Vedi l'ultima versione del contenuto originale in ingleseIf you have an idea for improving this documentation, please feel free to contribute by submitting a pull request on GitHub.
GitHub link to the documentationCopy doc Markdown to clipboard
Migrate from Svelte I18n to Intlayer
Moving your Svelte application from svelte-i18n to Intlayer takes just a moment using the compat adapter.
What to do
Simply run the initialization command in your project:
Copiare il codice nella clipboard
npx intlayer initThis generates intlayer.config.ts. Ensure your SvelteKit / Vite plugins are wrapped with Intlayer's alias plugin to seamlessly map svelte-i18n to @intlayer/svelte-i18n.
What it does under the hood
Svelte-i18n relies on heavily used stores ($_, $t, $format, etc.) and ICU MessageFormat.
Under the hood:
- Stores: Intlayer proxies the
svelte-i18nstores.$_becomes a derived store of the current locale returning an Intlayer resolver. - Keys: Your flat keys (e.g.
$_('home.title')) are evaluated such that the first path segment represents the Intlayer dictionary. - ICU Syntax: Fully handled by the shared ICU resolver (
intl-messageformatequivalent parsing). - Formatters:
$date,$time,$numbercalls redirect safely to Intlayer's native core formatters. - Babel/SWC Analysis: The Intlayer analyzer reads the Svelte store callers (
$_) inside your.sveltesource files before compilation to automatically build the relevant dictionary chunks.