i18next
DocsWith your agentBlog
i18nextreact-i18nextnext-i18nextAstroi18next-cliMore
i18next-cli ยท migrate-config
  • Introduction
  • Getting started
Commands
  • localize
  • init
  • extract
  • status
  • lint
  • types
How it works
  • Namespaces
  • Dynamic keys
  • Translation file formats
  • ICU and MF2 messages
  • Location metadata
  • CI and watch mode
  • Plugin system
Reference
  • Configuration
  • Global options
  • sync
  • instrument
  • rename-key
  • migrate-config
  • Locize commands
  • Supported patterns
  • Programmatic usage
Upgrading
  • Migration from i18next-parser
View as Markdown

migrate-config

Turn an i18next-parser configuration into an i18next-cli configuration.

Converts an i18next-parser.config.js file into an i18next.config.ts.

bash
npx i18next-cli migrate-config

# Using custom path for old config
npx i18next-cli migrate-config i18next-parser.config.mjs

The rest of the move, including the Node.js version: Migration from i18next-parser.

Previousrename-keyNextLocize commands
Edit this page
i18next

MIT licensed. Maintained since 2011.

With your agent

  • The conversation
  • Build a multilingual site
  • Add a second language
  • Client changes texts
  • Keep languages current
  • Findable languages
  • AI coding agents (docs)

Docs

  • i18next
  • react-i18next
  • next-i18next
  • Astro
  • i18next-cli
  • Blog

For agents

  • llms.txt
  • This page as .md
  • Agent skill
  • GitHub
Privacy