Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tree shake messages #2859

Open
3 of 4 tasks
GalacticHypernova opened this issue Mar 20, 2024 · 0 comments
Open
3 of 4 tasks

Tree shake messages #2859

GalacticHypernova opened this issue Mar 20, 2024 · 0 comments

Comments

@GalacticHypernova
Copy link

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

  • Would you be willing to help implement this feature?
  • Could this feature be implemented as a module?

Final checks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants