{i18n.t('welcome', { name: 'Alice' })}
\n{i18n.t('items', { count: 5 })}
\n```\n\nThe syntax is the [Curly Message Format](https://github.com/curly-message/spec).\nIts parser options โ custom modifiers, modifier defaults and a report channel โ\ngo under `config.parserOptions`:\n\n```javascript\nconst config = {\n parserOptions: {\n modifierDefaults: { number: { maximumFractionDigits: 2 } },\n onReport: (report) => console.warn(report.message, report),\n },\n loaders: [/* โฆ */],\n};\n```\n\nReports are silent by default; `onReport` is where you route them.\n\n### Server-side rendering\n\nBuild one instance **per request** on the server โ a module-level instance is\nshared between concurrent requests, which leaks one visitor's locale into\nanother's page. Export the config, and let each request build from it:\n\n```javascript\n// src/routes/+layout.server.js\nimport { I18n } from 'sveltekit-i18n';\nimport { config } from '$lib/translations';\n\nexport const load = async ({ url, locals }) => {\n const i18n = new I18n(config);\n\n await i18n.loadTranslations(locals.locale, url.pathname);\n\n return { locale: locals.locale, translations: i18n.snapshot() };\n};\n```\n\nThe client hydrates by handing that payload back through\n`config.translations`, so the loaders behind it do not run a second time. The\nfull wiring โ including the browser-side instance and passing it down through\nSvelte context โ is in the\n[Getting Started guide](./docs/GETTING_STARTED.md).\n\n## Documentation\n\n**๐ [Complete Documentation Index](./docs/INDEX.md)** โ Find everything in one place\n\n### Quick Links\n\n- ๐ [Getting Started Guide](./docs/GETTING_STARTED.md) โ 15-minute tutorial\n- ๐๏ธ [Architecture Overview](./docs/ARCHITECTURE.md) โ How everything works\n- ๐ [API Documentation](./docs/README.md) โ Complete reference\n- โจ [Best Practices](./docs/BEST_PRACTICES.md) โ Production-ready patterns\n- ๐ง [Troubleshooting](./docs/TROUBLESHOOTING.md) โ Common issues & FAQ\n\n## Examples\n\n> [!NOTE]\n> The examples still show the v2 API. Their rework is tracked in\n> [#230](https://github.com/sveltekit-i18n/lib/issues/230); until it lands, the\n> [Getting Started guide](./docs/GETTING_STARTED.md) is the reference for v3\n> wiring.\n\nExplore working examples for different use cases:\n\n- [Multi-page app](./examples/multi-page) โ Most common setup\n- [Locale-based routing](./examples/locale-router) โ SEO-friendly URLs (e.g., `/en/about`)\n- [Component-scoped translations](./examples/component-scoped-ssr) โ Isolated translation contexts\n- [Custom parsers](./examples/parser-icu) โ Using ICU message format\n- [All examples](./examples) โ Complete list of examples\n\n## Advanced Usage\n\n### Need a different parser?\n\nThis package wires `@sveltekit-i18n/parser-curly` and fills the core's `parser`\nslot itself, so a different message format means building on\n[@sveltekit-i18n/base](https://github.com/sveltekit-i18n/base) directly:\n\n```javascript\nimport { I18n } from '@sveltekit-i18n/base';\nimport parser from '@sveltekit-i18n/parser-icu';\n\nconst config = {\n parser: parser({ onReport: null }),\n // ... rest of config\n};\n```\n\nThat is the one case where installing the core directly is right โ you are then\nnot using this package at all. Learn more about\n[parsers](https://github.com/sveltekit-i18n/parsers).\n\n### Extensions\n\n`config.extensions` pipes the constructed instance through adapter functions,\nleft to right, and `new I18n(config)` evaluates to the last one's output. That\nis how the store surface ships:\n\n```javascript\nimport { I18n } from 'sveltekit-i18n';\nimport stores from '@sveltekit-i18n/extension-stores';\n\nexport const { t, locale, loading } = new I18n({ ...config, extensions: [stores] });\n```\n\n## TypeScript Support\n\nFull TypeScript support with complete type definitions for configuration and API:\n\n```typescript\nimport { I18n, type Config } from 'sveltekit-i18n';\n\nconst config: Config = {\n loaders: [\n // ... your loaders\n ],\n};\n\nexport const i18n = new I18n(config);\n```\n\nAnnotating the config (`const config: Config = โฆ`) widens it, which costs the\nlocale completion a config literal would have given `setLocale` and `l`. Pass\nthe literal straight to the constructor where you want that.\n\nTo have payloads checked, give the config a `schema` โ keys autocomplete and a\nwrong payload is a type error:\n\n```typescript\nimport { I18n } from 'sveltekit-i18n';\n\nconst i18n = new I18n({\n ...config,\n schema: {} as { 'common.greeting': { name: string } },\n});\n\ni18n.t('common.greeting', { name: 'Alice' }); // ok\ni18n.t('common.greting', { name: 'Alice' }); // Error: not a key of the schema\ni18n.t('common.greeting', {}); // Error: `name` is required\n```\n\nOnly the schema's **type** is read, so the slot may hold an empty value. A\nsingle payload type for every message is stated through the type arguments\ninstead:\n\n```typescript\nimport { I18n, type Config } from 'sveltekit-i18n';\n\ntype Payload = { name: string };\n\nconst config: Config