Jan Amann

Thanks for showing interest here @kelkes! There are unfortunately a few other priorities for the coming months. Multi-tenancy is already supported to a certain degree, but the `/[tenant]/[locale]` use case...

Hey, thanks for proposing this! I think it's a good point to mention this, but I'd considerably give this less prominence in the docs. I think instead of a separate...

Did you by chance have a moment to think about this again @kjartanhr? See [my feedback above](https://github.com/amannn/next-intl/pull/1161#issuecomment-2200818820).

I agree it could be useful, but `next-intl` currently depends on `intl-messageformat` which unfortunately doesn't support this (I think because it's not spec'ed by ICU). The alternative is: ```tsx t('list',...

I'd be interested in this too! I guess this is required for #820 (if namespaces are used).

It seems like at least programmatically this should be possible: https://github.com/lokalise/i18n-ally/blob/0ea030d0097370a1268e2c915b295bdf7d1c9ad8/src/frameworks/react-i18next.ts#L82-L108

I see your point, yes. While technically we could provide a default for `useFormatter`, we can currently not apply one when formatting a number as part of a message. That's...

Hmm, I see your point. I'm not sure if accessing a string is the best option here though. The canonical way to access search params in Next.js is either the...

Hmm, good point—I saw though that nuqs seem to move to URLSearchParams-style array support: https://github.com/47ng/nuqs/discussions/484. Might be worth keeping an eye on that. For working with `Link`, nuqs suggests a...

Hey, it seems like your branch is based on an outdated state of `main`: With https://github.com/amannn/next-intl/pull/1814, @remcohaszing switched `global.d.ts` to `global.ts`. Does that avoid the issue you want to address...