Jan Amann

Hmm, that's interesting. The Next.js 15 release is scheduled for next week as far as I know, maybe worth waiting until then. It might be that they're still ironing out...

I've just upgraded two examples in https://github.com/amannn/next-intl/pull/1089 to Next.js 15 RC and React 19 RC. Generally this seems to work, but it looks like the issue you are seeing comes...

Side note for those living on the bleeding edge: The test suite from `next-intl` discovered that serving sitemaps might be broken in Next.js 15 RC (see https://github.com/vercel/next.js/pull/65507#issuecomment-2128974838)

@makoveckib Yep, I've written a detailed analysis about this in https://github.com/amannn/next-intl/issues/1375 and a canary release is already available with the relevant changes if someone wants to test it: https://github.com/amannn/next-intl/pull/1391.

There’s some minimal migration necessary if you want to get rid of the warnings, please refer to the linked PRs in the release PR.

I just gave Next.js 15 RC 2 a shot, and while some things have improved, it seems like there is still a bug on their end: https://github.com/vercel/next.js/issues/69000#issuecomment-2416459189. So be careful...

@wottpal Yep, that's the latest one! If you install `next-intl@canary` that should always give you the most recent one. Regarding `3.22.0-canary.1`: That's a slightly outdated one, I had to adapt...

**Update**: I'll wait with updating docs and examples for Next.js 15 for the time being since there's [a critical bug](https://github.com/amannn/next-intl/issues/1442) in Next.js 15 that affects multilingual apps that use i18n...

next-intl can surely be updated to the latest version, I only found that Next.js 15 has a bug with alternate links (see above). Additionally, I found this one the other...

Hey @ArthurLobopro, thank you for your reply here! Would be happy to switch, but how can I highlight specific lines with your extension? I gave it a go, but couldn't...