Fix crash in DateRangePicker when using SSR optimized localized strings #6286
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.
In our Next.js example app, when selecting a range in a DateRangePicker with reversed order, the page would crash with an error about a missing localized string. In that setup, the optimize-locales-plugin is used to remove all localized strings from the JS bundle, and they are injected into the page during SSR. However, this particular code used the dictionary imported from the JS bundle, and did not load the global dictionary from the window like other parts of the code.