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
First of all, I hope this is the correct place to ask the question. If not, please guide me to the correct place :)
I been a long time fan of the product and the fact you are open source is a source of inspiration so thank you!
I'm starting a migration from the pages router to the app router and since we have a lot of pages I wanted to build a migration story but running into a lot of problems with the i18n config in next.config.js and the fact that it don't play well with the app router - here.
I was looking at your cal.com app code and it looks like you have a working solution. I looked all over the code but could not find where the dynamic section of the pathname [lang] / [locale] is located to be able to accomplish it in the app router.
And when I tested it with the middleware I have conflicts and infinite redirects clashes between the i18n config setting and the middleware logic to try and make them work.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
First of all, I hope this is the correct place to ask the question. If not, please guide me to the correct place :)
I been a long time fan of the product and the fact you are open source is a source of inspiration so thank you!
I'm starting a migration from the pages router to the app router and since we have a lot of pages I wanted to build a migration story but running into a lot of problems with the
i18n
config in next.config.js and the fact that it don't play well with the app router - here.I was looking at your cal.com app code and it looks like you have a working solution. I looked all over the code but could not find where the dynamic section of the pathname [lang] / [locale] is located to be able to accomplish it in the app router.
And when I tested it with the middleware I have conflicts and infinite redirects clashes between the i18n config setting and the middleware logic to try and make them work.
Any help will be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions