Jan Amann

Thank you very much for this detailed feature request! I agree there's a piece missing here currently. I've opened https://github.com/amannn/next-intl/issues/653 to collect this issue together with similar ones, also to...

@cbodin I've updated https://github.com/amannn/next-intl/issues/653 with a proposal that I think could support your use case. Let me know in the linked issue in case you have feedback or a better...

I'll close this now in favor of #653. This issue is mentioned there and will be taken care of.

There's another update coming to the Supabase authentication docs here: https://github.com/amannn/next-intl/pull/1260

Good question! There's unfortunately a bit of a conflict in the Next.js docs in regard to the root layout. The docs mention that it's required to have a layout with...

You don’t need to call the function in client-only pages.

Unfortunately not, please see the corresponding docs: [Add `unstable_setRequestLocale` to all layouts and pages](https://next-intl-docs.vercel.app/docs/getting-started/app-router#add-unstable_setrequestlocale-to-all-layouts-and-pages). It might work in some cases, but there's a race condition. To work reliably, you should...

We'll probably introduce support for providing a locale to `next-intl` as an alternative to having to use the middleware to negotiate this (see https://github.com/amannn/next-intl/pull/1017). If your app only supports a...

A realization while working on https://github.com/amannn/next-intl/pull/1017: We currently support a `defaultLocale` that is used as a fallback when matching locales in the middleware. However, the `defaultLocale` only applies to this...

Hey @vordgi! Nice to hear from you here, been following your work with nimpl-getters! :) Can you by chance provide a reproduction where you observe that the context is lost?...