feat!: next-intl@4
#1412
Draft
feat!: next-intl@4
#1412
+4,442
−7,144
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
This reverts commit 47239f9.
…currently active pathname for localized pathnames
# Conflicts: # packages/next-intl/src/middleware/utils.test.tsx # packages/next-intl/src/shared/utils.test.tsx
…is rendered from a Server Component (#1191) 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 `formats` object that you don't want to pass to the client side), you can manually opt-out via `formats={{}}` on `NextIntlClientProvider` in 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 `NextIntlClientProvider` in a Server Component, you rely on static rendering, but you're not using `unstable_setRequestLocale` (i.e. you're using hooks like `useTranslations` exclusively in Client Components), this can opt your page into dynamic rendering. If this affects you, please provide the `formats` prop explicitly to `NextIntlClientProvider`.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
If you have nested providers, previously only the configuration of the innermost one would be applied. With this change, configuration is now passed from one provider to the next, while allowing to override individual props. **BREAKING CHANGE:** There's a very rare chance that this change affects your app, but in case you've previously relied on providers not inheriting from each other, you now have to reset props manually in case you want to retain the prev. behavior.
# Conflicts: # packages/next-intl/.size-limit.ts
…gument (#1561) These are errors now: ```tsx t('message', {value: null}); t('message', {value: undefined}); t('message', {value: false}); ``` If you really want to put a raw boolean value in a message, you can cast it to a string first: ```tsx const value = true; t('message', {value: String(value)}); ```
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.
After a year of feature development, this release mostly aims to clean up the API surface to ensure
next-intlremains lean—there should be no surprises.Changes
Locale#1495useMessages&getMessages#1489NextIntlClientProviderinstances are present #1413formatswhenNextIntlClientProvideris rendered from a Server Component #1191localeto be returned fromgetRequestConfig#1486localeCookie: falseis set #1487now={new Date()}fromNextIntlClientProviderfor usage withformat.relativeTime(preparation fordynamicIO) #1536NextIntlClientProviderfor usinguseLocaleon the client side (preparation fordynamicIO) #1541null,undefinedorbooleanas an ICU argument #1561typescriptversion to 5 for projects using TypeScript #1481TODO
nownext-intl@4.0#1485 once we know if these are the only missing deprecation warnings.setRequestLocale#663 (comment). It's not strictly blocking anything.Related
Resolves #1153
Resolves #1452
Resolves #410
Resolves #779
Resolves #1464