Jan Amann

Small docs update: There's now a page that provides instructions for [runtime requirements and polyfills](https://next-intl-docs.vercel.app/docs/usage/runtime-requirements-polyfills).

Maybe messages can be rendered exclusively on the server: https://github.com/amannn/next-intl/issues/1#issuecomment-750297944

`next/dynamic` can be used to lazy load client code for a React component. But how would you integrate that with fetching the messages for a particular locale? I think with...

But that would require you to load messages for unused locales as well, right? Also I think the messages would only be loaded as soon as the module code is...

> dynamic does not load anything until the dynamic component is rendered I also think that's true, but it assumes that what you're wrapping with `dynamic` is a component. It...

During the Next.js Conf this week, the Vercel team has shown a brief demo on how data could be fetched at a component-level at arbitrary levels in the tree. This...

Yep, exactly – that's similar to what I had in mind as well. I first thought about having an endpoint that provides messages, but if we can transfer context from...

Thanks for opening this! I have a bit of experience with i18next but from what I saw so far it is similar in things like interpolation, but differs quite a...

There's [`Intl.MessageFormat` on the horizon](https://github.com/tc39/proposal-intl-messageformat) which uses the Message Format 2 syntax. It's still under heavy development, but if this makes it into the browsers that is probably a format...

@jamuhl I'm sorry, I can't follow how that is related to this issue? Also please note that `next-intl` is not affiliated with i18next.