Jan Amann

@shadowlik That's so cool! I'm a passionate runner myself, keep up the good work! 🙌

@kneza23 > We are currently researching possible solutions but `next-intl` seems like it would our choice on our new project. Do you have an advice how to connect external API...

I haven't personally looked into integrating with the Crowdin JS API but it should certainly be possible. In the places where in the documentation a JSON file is loaded from...

> We're using `next-intl` on https://watershed.com! It's running entirely on App Router, using the Client Components version. @lachlanjc Oh wow, that's so cool! Really happy to see `next-intl` being used...

@ovflowd Oh my god, that's soo cool to hear! Thank you so much for leaving a note here! And definitely reach out in case you run into something that you...

@ovflowd Thank you for the detailed feedback, this is really helpful! To address your points in order: 1. I think there's some inconsistency currently on the Next.js side: https://github.com/vercel/next.js/issues/55735#issuecomment-1733611397. I...

Thanks! Yep, as mentioned I'd be ok with this change as long as the bundle size doesn't grow. Can you fix the invalid regex?

Briefly looking through your example, I see two issues: 1. `[locale]/page.tsx` doesn't use `unstable_setRequestLocale` 2. `[locale]/test/page.tsx` doesn't _call_ `unstable_setRequestLocale` Can you fix that and verify it fixes the bug?

You currently don't have `unstable_setRequestLocale` on `[locale]/page.tsx` but `generateStaticParams` in `[locale]/layout.tsx` tries to generate that page. So I'd say there's an inconsistent configuration in your reproduction, right? As a side...

I currently don't have experience with v5. We have [an example within this repo](https://github.com/amannn/next-intl/tree/main/examples/example-next-13-next-auth) as well as [documentation on usage with v4](https://next-intl-docs.vercel.app/docs/routing/middleware#example-auth-js). Would you be interested in setting up a...