Version Packages - #192
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
29 times, most recently
from
August 4, 2026 08:41
1448caf to
29cf1c0
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
August 4, 2026 13:13
1b46d1d to
371473c
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 9, 2026 10:58
371473c to
729c0d5
Compare
This file contains hidden or 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
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 PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@better-i18n/core@0.14.0
Minor Changes
36e67fa: Stop re-downloading every namespace on the client when SSR already delivered the messages.
BetterI18nProviderused to callgetMessages(locale)on every mount, with no namespace scope, even when the SSR/prop payload already matched the active locale. On a prerendered site each new document starts with an empty in-memory cache, so that was a full re-fetch of the data the user was already looking at — and because no namespaces were passed, it asked for every namespace the manifest declares.Two changes:
revalidate, ETag-aware, typically a single 304) scheduled at idle, instead of a payload download.namespacesprop it already declared in its type, passing it togetMessagesandrevalidateso client fetches stay as narrow as the server load.I18nCore.revalidatetakes an optional{ namespaces }argument so the refetch after a version change matches the scope of the original load. Existing calls are unaffected — it defaults to thenamespacesgiven tocreateI18nCore.Patch Changes
getMessagessilently returning a partial namespace set when the CDN batch endpoint truncates its response (e.g. when the combined payload is large, dropping alphabetically-later namespaces). The batch response is now required to contain every requested namespace; on any shortfall the SDK rejects it and falls back to individual per-namespace fetches (one request each, no aggregate size cap), so pages never render with missing translations.@better-i18n/use-intl@0.10.0
Minor Changes
36e67fa: Stop re-downloading every namespace on the client when SSR already delivered the messages.
BetterI18nProviderused to callgetMessages(locale)on every mount, with no namespace scope, even when the SSR/prop payload already matched the active locale. On a prerendered site each new document starts with an empty in-memory cache, so that was a full re-fetch of the data the user was already looking at — and because no namespaces were passed, it asked for every namespace the manifest declares.Two changes:
revalidate, ETag-aware, typically a single 304) scheduled at idle, instead of a payload download.namespacesprop it already declared in its type, passing it togetMessagesandrevalidateso client fetches stay as narrow as the server load.I18nCore.revalidatetakes an optional{ namespaces }argument so the refetch after a version change matches the scope of the original load. Existing calls are unaffected — it defaults to thenamespacesgiven tocreateI18nCore.Patch Changes
@better-i18n/expo@0.9.1
Patch Changes
@better-i18n/next@0.9.1
Patch Changes
@better-i18n/remix@0.6.9
Patch Changes
@better-i18n/server@0.4.8
Patch Changes
@better-i18n/vite@0.2.13
Patch Changes
docs@0.0.12
Patch Changes
hono-example@0.0.23
Patch Changes
hydrogen-demo@0.0.19
Patch Changes
expo-native@1.0.34
Patch Changes