feat!: Automatically inherit formats when NextIntlClientProvider is rendered from a Server Component
#1191
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…ard-formats # Conflicts: # docs/pages/docs/environments/server-client-components.mdx # packages/next-intl/package.json
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should ease the transition from Server to Client Components, as you don't have to manually pass this prop anymore. If you've previously passed this prop manually, you can remove this assignment now.
If this is not desired (e.g. because you have a large
formatsobject that you don't want to pass to the client side), you can manually opt-out viaformats={{}}onNextIntlClientProviderin order to not provide any formats on the client side.BREAKING CHANGE: There's a very rare chance where this can break existing behavior. If you're rendering
NextIntlClientProviderin a Server Component, you rely on static rendering, but you're not usingunstable_setRequestLocale(i.e. you're using hooks likeuseTranslationsexclusively in Client Components), this can opt your page into dynamic rendering. If this affects you, please provide theformatsprop explicitly toNextIntlClientProvider.