Frameworks
Nuxt
Your locales come from whatever @nuxtjs/i18n already resolved — every layer, every app in a monorepo. There is nothing to configure.
Make It Faster
Without help, the CLI loads your Nuxt app to find out what it resolved. Installing the module publishes that during your build instead:
npm install -D @the-i18n-kit/nuxt
See the Nuxt module. It also removes the need for @nuxt/kit to be installed, and for the app to load at all — which matters in CI, where a nuxt.config.ts that needs environment variables can fail.
Overrides
| What you want | How |
|---|---|
| Restrict or reorder locales | locales in your kit config |
| Force this adapter | framework: 'nuxt' |
defaultLocale in your kit config is ignored here. Nuxt owns it — set i18n.defaultLocale in nuxt.config.ts.Limits
- A config that will not load, fails. If
nuxt.config.tsneeds environment variables the CLI does not have, resolution fails the waynuxt buildwould. Install the module and build in CI. - Apps nested more than four directories deep are not found. Point the CLI at one with
--projectDir, or run it from inside. - Policy does not go in
nuxt.config.ts. Glossary, protected locales and scan rules belong in your kit config, which is read without a build.