fix: Correctly detect base path at the app root / when using a locale prefix strategy other than always. This ensures the locale cookie is set correctly.

[amannn]

Fixes #997

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
next-intl-docs	✅ Ready (Inspect)	Visit Preview	Apr 17, 2024 11:09am
next-intl-example-app-router	✅ Ready (Inspect)	Visit Preview	Apr 17, 2024 11:09am

[130db]

Interesting!
Can not upgrade to 3.11.2 or higher after this fix.

Here is my autogenerated config.

const locales is not casted with "as const" because line 9 will fail in i18n.ts

[ghost]

We experience the same problem with the same config parameters as above.
cc @amannn any idea? It looks like some basic misconfiguration, but where..

[130db]

Yes! I fixed it.

Tried different approach by following Mohammad's tutorial
https://phrase.com/blog/posts/next-js-app-router-localization-next-intl/

Did POC on fresh NextJS install and then tried to replicate on my website.
Guess what, it failed :D with

TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed

The problem is:
When you use async page and call await getTranslations it fails.

Solution
Make page non-async and replace getTranslations with useTranslations
Move every other await to coresponding component