Jan Amann

Closing due to inactivity …

**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...

@ChristianIvicevic Thanks for the note! Yeah, I hope Next.js addresses the upstream issues that were introduced in Next.js 15 so I can start recommending it without drawbacks! :)

From https://github.com/facebook/react/issues/32392: > cloneElement is basically soft deprecated. It works against any ability to optimize by inlining. One form of inlining is Server Components so it's hard for the client...

@francoismassart Any chance you have time for a quick review here?

I just ran into the same issue. Here's a reproduction: https://github.com/amannn/bunchee-test/commit/a9e6ce62d5f8ff0d99a3f3ee0b0a7c00fdee592a The relevant part is that there's a type created in the shared runtime that is then referenced in an...

Many thanks for the thoughtful bug report and reproduction! Do you think you could report this upstream in the Next.js repo? Seems like this is something to be addressed there....

Thanks a lot, I'll keep an eye on the issue!

There are currently two issues open for the same topic, I'll close this in favor of https://github.com/amannn/next-intl/issues/1442. I noticed also `next/image` with `priority` causes the same error.

If you want to add a layout at the root, it shouldn't include tags like `html`, but simply return children (see [the docs](https://next-intl.dev/docs/environments/error-files#catching-non-localized-requests)). Based on my latest tests, this layout...