Jan Amann

@bryanltobing In Server Components, there's no need for lazy loading messages, since the performance will not be impacted by loading the translations for your whole app. Are you interested in...

The messages that are loaded server side depend on what you load in [`i18n.ts`](https://next-intl-docs.vercel.app/docs/next-13/server-components#global-request-configuration). On the client side it depends on [what you pass to `NextIntlClientProvider`](https://next-intl-docs.vercel.app/docs/next-13/server-components#using-interactive-state-in-translations). You can optimize both...

That's a great question @kneza23! I'm currently working on a [major docs update](https://github.com/amannn/next-intl/discussions/351) and have added a page that should hopefully answer this: [Internationalization of Server & Client Components in...

Hmm, which aspects remain unanswered for you? The page is structured into three sections: 1. [Passing translations to Client Components](https://next-intl-docs-git-docs-app-router-first-next-intl.vercel.app/docs/environments/server-client-components#passing-translations-to-client-components) (recommended, if possible) 2. [Using interactive state in translations](https://next-intl-docs-git-docs-app-router-first-next-intl.vercel.app/docs/environments/server-client-components#using-interactive-state-in-translations) (discusses...

Right, I understand! Your code looks fine to me. My main point with the page I've linked to is to explain the tradeoffs for different techniques that allow handling translations...

I just stumbled over the [TanStack Query nextjs-suspense-streaming example](https://codesandbox.io/p/sandbox/github/tanstack/query/tree/beta/examples/react/nextjs-suspense-streaming?embed=1&file=%2Fsrc%2Fapp%2Fpage.tsx%3A21%2C1-22%2C1) ([tweet](https://twitter.com/TkDodo/status/1680153231853223938)). Based on the implementation I'm wondering if we could: 1. Expose an endpoint that returns requested messages by namespace 2....

@santyas The polyfills? Just as shown here: https://next-intl-docs.vercel.app/docs/production-checklist#runtime-requirements. But definitely verify if you need any polyfills at all, depending on the browsers you support.

We have many more links to examples now in the docs, and with that, the list from the top of this issue is quite complete. I'll close this issue therefore....

@francoismassart Any chance this could be merged?

Great to see some people interested in this idea! @rattrayalex What would you suggest how this could be integrated? With or without an option? Having it be skippable with `prettier-ignore`...