Pose una domanda e ottieni un riassunto del documento facendo riferimento a questa pagina e al provider AI di tua scelta
Cronologia delle versioni
- "Init history"v9.0.013/06/2026
Il contenuto di questa pagina è stato tradotto con un'IA.
Vedi l'ultima versione del contenuto originale in ingleseIf you have an idea for improving this documentation, please feel free to contribute by submitting a pull request on GitHub.
GitHub link to the documentationCopy doc Markdown to clipboard
Migrate from Next Translate to Intlayer
Migrating from next-translate to Intlayer is a near drop-in replacement that retains your existing syntax and tags.
What to do
Initialize Intlayer in your project:
Copiare il codice nella clipboard
npx intlayer initThe CLI will scaffold your configuration. You can then apply the Intlayer plugin in your next.config.ts, which injects build-time subpath aliases mapping next-translate/useTranslation to @intlayer/next-translate.
What it does under the hood
next-translate provides hooks like useTranslation('ns'), t('ns:key.path'), and the <Trans> component.
Under the hood:
- Interpolation & Plurals: It relies closely on the
react-i18nextadapter behavior. Handled dynamically are{{var}}placeholders and pluralization mapped from suffixes likekey_0,key_one, andkey_other. <Trans>component: Directly supported for HTML-ish tag parsing alongside an array-basedcomponentsprop.- Namespaces: Subpath aliasing ensures that your
useTranslationreferences the correct internal dictionary namespaces without manual modification.