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
In an app with a lot of translatable content importing the whole language file, even if lazily, will introduce huge network overhead, and most of the time would even be unnecessary, as there will likely be a slight portion of the messages in use for every page. Furthermore, it could introduce data leaks, the most notable example being admin pages having their translation sent to the client. Tree shaking the messages will ensure there is minimal overhead and minimal data sent to the client, which will not compromise data integrity and still allow to use lazy loading as much as possible.
Additional information
Would you be willing to help implement this feature?
Could this feature be implemented as a module?
Final checks
Read the contribution guide (The contribution guideline of nuxt-modules/i18n is compliant with Nuxt too).
Describe the feature
In an app with a lot of translatable content importing the whole language file, even if lazily, will introduce huge network overhead, and most of the time would even be unnecessary, as there will likely be a slight portion of the messages in use for every page. Furthermore, it could introduce data leaks, the most notable example being admin pages having their translation sent to the client. Tree shaking the messages will ensure there is minimal overhead and minimal data sent to the client, which will not compromise data integrity and still allow to use lazy loading as much as possible.
Additional information
Final checks
The text was updated successfully, but these errors were encountered: