Jan Amann

No worries! Yep, I agree that scoping translations is helpful. next-intl is heavily based on that too! 🙂

Thanks for the report! Just found this, there seems to be a limitation in TypeScript: https://github.com/microsoft/TypeScript/issues/40803. When generating a union based on a type, the number of elements is limited...

Thank you so much for analyzing the bug and creating a good reproduction! Hopefully this gets fixed soon on the Next.js side! 🙏

> I thought we had to create our own with `createLocalizedPathnamesNavigation` and `createSharedPathnamesNavigation` from the `next-intl/navigation` package. Yep, that's the case. The reproduction above uses an older pre-release beta version...

Seems like this was [resolved upstream](https://github.com/vercel/next.js/issues/53147#issuecomment-2149375685).

I'm closing this for the time being, we can re-open if necessary to try out potential fixes.

Hey @dtrucs and thanks for the report! Does your example work without `next-intl`? I also tried out parallel routes in one of the examples in this repository and got really...

https://github.com/vercel/next.js/pull/51526 was merged, but not released yet in a stable version AFAIK. Once it is, it would be helpful if someone could confirm that this fixes this issue discussed in...

Hmm, that's unfortunate. I guess if you remove `next-intl` from the reproduction (but keep `[locale]`), the Next.js team might be thankful for a bug report.

I don't have experience with `next-connect`, but if someone is interested in adapting the middleware accordingly and this doesn't have any negative side effects for the standalone usage (same API,...