Documento original del Skill
Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.
Nuxt I18n
Nuxt I18n owns locale messages, localized routes, language detection, and locale metadata. Nuxt owns the surrounding page, rendering, and server lifecycle.
Workflow
- Inspect the installed
@nuxtjs/i18nversion,nuxt.config.*,i18n/i18n.config.*, locale files, and affected pages. The setup is understood when locale codes, files,defaultLocale, and the routing strategy agree. - Open the smallest matching guide below. Keep module options in
nuxt.config, Vue I18n options ini18n.config, and translated messages in locale files. - Implement with localized links and module composables so routing, message loading, and SEO share one locale state.
- Run
nuxi prepareand the project's typecheck, then visit the affected route in the default and one secondary locale. The change is complete when both locales render the expected message, URL, language metadata, and fallback behavior.
Routing
| Task | Open |
|---|---|
| Installation, locale objects, file layout, browser detection, or Vue I18n config | Configuration |
| Translation keys, interpolation, plurals, dates, numbers, or runtime message loading | Messages |
| Route strategies, localized links, switchers, custom paths, dynamic slugs, or SEO | Routing and SEO |
| Nuxt pages, middleware, data fetching, SSR state, or server routes | nuxt skill |
Baseline
bash
npx nuxi@latest module add @nuxtjs/i18nts
export default defineNuxtConfig({
modules: ['@nuxtjs/i18n'],
i18n: {
defaultLocale: 'en',
locales: [
{ code: 'en', language: 'en-US', name: 'English', file: 'en.json' },
{ code: 'fr', language: 'fr-FR', name: 'Français', file: 'fr.json' },
],
},
})json
{
"welcome": "Welcome"
}Locale files resolve from i18n/locales/ by default. Use the same locale code in configuration, route helpers, locale files, and fallback rules.
