improvement: add custom webpack configuration #2
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
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 improves the bundling of the assets that are used by the web components (like translations, locale specific data for the calendars).
Currently (with no custom webpack configuration) they are inlined all.
However, they are language specific so you never need all of them at runtime (if we inline the CLDR data for the calendars, the bundle size grows from 135 KB to 1.6 MB). So we chose to fetch these resources dynamically at runtime.
For this option, we would have to know the URLs, so we can fetch the specific file according to the current language.
This custom configuration is explained in our sample project