Lazy load translations and date-fns, server side support for "Browser Default" language #2380
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.
Description
Lazy loads i18n translations and date-fns using dynamic imports.
Before
Both scripts are always loaded.
After
For "en-US" only
client.js
is loaded. "en-GB" and "en-CA" additionally load onedate-fns-*client.js
, Most languages load onetranslation-*.client.js
and onedate-fns-*.client.js
. Languages like "pt-BR", for which a specific (pt-BR) and general (pt) translation exists, load two translations and one date-fns.date-fns
are picked to match the language that i18n uses.Uses the "Accept-Language" header to determine which language to use for server side rendering. This also allows to load translations and date-fns in parallel with
client.js
.The language code for "pt-BR" is no longer "pt_BR".
"DOMContentLoaded" (used for Notification permission) started working when only
client.js
is needed.