You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are currently some issues with the internationalization library that is being used.
1 - High memory usage during build time
2 - A large app.js bundle is being created, making the user experience suffer when this is downloaded
After some initial fixes for code splitting which was contributing to the large app.js bundle, it was uncovered that more needs to be done to fix this.
Currently this is an analysis of these bundles:
Ideally, we can split out translation bundles:
To reproduce
Build the app and analyze the bundles
Expected behavior
Get to a point where languages are being broken out into their own bundles, and we no longer have them in one app.js bundle.
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
This is part of our Change i18n plugin epic.
Describe the bug
There are currently some issues with the internationalization library that is being used.
1 - High memory usage during build time
2 - A large app.js bundle is being created, making the user experience suffer when this is downloaded
After some initial fixes for code splitting which was contributing to the large app.js bundle, it was uncovered that more needs to be done to fix this.
Currently this is an analysis of these bundles:
Ideally, we can split out translation bundles:
To reproduce
Build the app and analyze the bundles
Expected behavior
Get to a point where languages are being broken out into their own bundles, and we no longer have them in one app.js bundle.
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: