How to seamlessly migrate from next-i18next to next-intl?

[patrikzita]

Hi there, 👋

I'm currently using next-i18next in my Next.js project for handling internationalization (i18n), but I'm considering migrating to next-intl due to some of its features and flexibility. However, I'm unsure of the best approach for making this migration smooth and without breaking my existing functionality.

Next.js version: 14.2
I have something about 12 pages. I use pages router and I'd like to migrate to app router with next-intl.

My goal is to have a smooth transition with minimal disruption to the existing user experience. Any help, examples, or insights from those who have experience with this would be greatly appreciated! 🙏

[amannn]

I don't have personal experience with this migration, but there are a few people on the issue tracker who have done this (e.g. #1306) — maybe if you have a specific question, they could help out.

Note that next-intl works both in the App Router as well as the Pages Router. You could consider migrating to next-intl in the Pages Router first and then later adopt the App Router.

[patrikzita]

Thank you, for your answer. I´d like to stay at next-i18next in Pages Router, but have only new pages in App Router. However, I find "collision" how setup next.config.js/next.config.ts, because next-i18next wants I18n object in next configuration and next-intl tempted us don´t use it there. Any recommendation how to make it work side by side?

[amannn]

Sounds pretty much like what @SLMNBJ has achieved here: #1306 (reply in thread)

[patrikzita]

I'll try catch up his solution.. Thanks.