Internationalize Nuxt applications with @nuxtjs/i18n. Use when configuring locales or browser detection, translating messages or routes, building locale switchers, handling fallbacks, lazy-loading messages, or adding locale SEO.
Nuxt I18n owns locale messages, localized routes, language detection, and locale metadata. Nuxt owns the surrounding page, rendering, and server lifecycle.
@nuxtjs/i18n version, nuxt.config.*, i18n/i18n.config.*, locale files, and affected pages. The setup is understood when locale codes, files, defaultLocale, and the routing strategy agree.nuxt.config, Vue I18n options in i18n.config, and translated messages in locale files.nuxi prepare and 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.| 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 |
npx nuxi@latest module add @nuxtjs/i18nexport 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' },
],
},
}){
"welcome": "Welcome"
}Locale files resolve from i18n/locales/ by default. Use the same locale code in configuration, route helpers, locale files, and fallback rules.
bc438e5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.