You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to localize pathnames (as in https://next-intl-docs.vercel.app/docs/routing#pathnames) with next-intl in a next 13.3.1 that uses Pages Router but can't seem to get it working. Is it possible to do that? if yes, could you provide an example for that use case? if no, could you update the docs to specifically mention a limitation in that regard?
The text was updated successfully, but these errors were encountered:
Maybe the App Router Migration example could provide a base for this as it shows how the i18n routing functionality of next-intl can be used with the Pages Router. Hope that helps!
if anyone is curious, looks like it's "kind of" possible https://github.com/Gieryneck/pages-router-next-intl-poc but since the i18n is removed from next.config the locale must be taken from the url path (the localePrefix cannot be 'never'). And I don't see a way of getting locale on _error.tsx page
Link to page
https://next-intl-docs.vercel.app/examples
Describe the problem
I'm trying to localize pathnames (as in https://next-intl-docs.vercel.app/docs/routing#pathnames) with next-intl in a next 13.3.1 that uses Pages Router but can't seem to get it working. Is it possible to do that? if yes, could you provide an example for that use case? if no, could you update the docs to specifically mention a limitation in that regard?
The text was updated successfully, but these errors were encountered: