@the-i18n-kit/nuxt

Nuxt module for the i18n kit.

Nuxt already resolves your layer graph and your locale table. This module publishes what Nuxt resolved as a build artifact the CLI reads in preference to hand-written config, so the derived half of your configuration stops being written twice.

📖 Documentation

Install

pnpm add -D @the-i18n-kit/nuxt

// nuxt.config.ts
export default defineNuxtConfig({
  modules: ['@nuxtjs/i18n', '@the-i18n-kit/nuxt'],
})

Then remove locales, localeDirs and defaultLocale from your kit config — the module derives all three, and declaring them by hand now fails the build. In a monorepo, register it in each Nuxt app.

What It Does

On nuxt prepare, nuxt dev and nuxt build it writes .nuxt/i18n-kit.json describing this app: its locale table, its layers, and which of those carry translations. It also fails the build on a protectedLocales entry that resolves to no locale or to several.

Kit policy — glossary, tone notes, protected locales, orphan-scan patterns — lives in i18n-kit.config.ts or .i18n-mcp.json, not here, so it applies in a checkout that has never built.

Removing the module is safe: the CLI falls back to loading the app through Nuxt, which is what it does for every project without it.

The module does not touch ESLint. To lint i18n calls with @nuxt/eslint, add the addon from the plugin yourself:

// nuxt.config.ts
import { i18nKitEslintAddon } from '@the-i18n-kit/eslint-plugin-vue/nuxt'

export default defineNuxtConfig({
  modules: ['@nuxt/eslint'],
  hooks: { 'eslint:config:addons': addons => addons.push(i18nKitEslintAddon()) },
})

→ The artifact, the two module options, and every fallback case

Development

playground/nuxt in this repo is the dev target.

pnpm --filter @the-i18n-kit/nuxt build
pnpm --filter playground exec nuxt prepare
cat playground/nuxt/.nuxt/i18n-kit.json

License

MIT