I18n is now just a plain dynamic path

[brisk bolt]

Hi @jolly falcon. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

[jolly falcon]

it's confusing.

previously, next.js allowed a default locale for i18n which allowed domain.com to remain as-is.

now all my customers, if they want to upgrade to next latest, must come to understand that all their link must be prepended with en/ ? without any guide from next.js? they literally pulled out a feature.

I'm finding it hard to believe this is truly a permanent change

[brisk bolt]

Sorry @jolly falcon, I seem to be having a bit of trouble. Don't worry though, I've pinged my supprt and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

[valid tundra]

It’s a dynamic path so you can customise it however you want. For that question, you can use middleware for example, capturing all requests without the locale and rewrite them to the correct locale based on headers for example

Now it’s just a matter of how you integrate nextjs features to the dynamic path and make it work the way you want it to