Example: Incremental adoption of App Router from Pages Router with next-intl

[mohitb35]

Is your feature request related to a problem? Please describe.

I'm trying to migrate to the app router - currently all pages in my app use the pages router.

I tried out the examples for app router and pages router individually and they worked. If I combine them however (which is required to do a gradual migration), things break.

I either run into a multiple redirect issue (when the locale is part of the url), or the locale detection does not seem to work.

Describe the solution you'd like

A minimal example you can provide to use app router and pages router simultaneously with next-intl would be useful.

Describe alternatives you've considered

I've searched for a possible solution within the next-intl docs , github issues on the next-intl repo, and stackoverflow, but have not found anything.

[amannn]

Update: The App Router migration example now shows a working approach.

See also: vercel/next.js#57704 (comment)

[mohitb35]

Thanks for the quick response @amannn .

I'll be able to try this out only after 22nd Nov as I have a few urgent tasks to complete. Will get back if it works, or if I need some clarification.

[amannn]

Sounds good! I'll close this ticket for the time being then, since we already have an example and the new docs will feature it more prominently. In case something doesn't work as expected, feel free to open a new issue!