Creation:2026-06-13Last update:2026-06-13
将此文档参考到您的 AI 助手ChatGPTClaudeDeepSeekGoogle AI modeGeminiPerplexityMistralGrok
使用您最喜欢的AI助手总结文档,并引用此页面和AI提供商
版本历史
- "Init history"v9.0.02026/6/13
此页面的内容已使用 AI 翻译。
查看英文原文的最新版本Edit this doc
If 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
Copy 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:
bash
复制代码
复制代码到剪贴板
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.