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

Code splitting #72

Closed
felixgirault opened this issue Sep 27, 2021 · 1 comment
Closed

Code splitting #72

felixgirault opened this issue Sep 27, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@felixgirault
Copy link
Contributor

Splitting Orejime into multiple files could reduce the downloaded weight by a great factor in nominal use cases.
The most gain would be attained by splitting it in two parts:

  • The core that would contain the pure mechanics: config, storage and DOM manipulation
  • The UI that would get loaded only if user interactions are needed.

This way, the first time a user would visit a site, the core would load, detect that user consent is needed, and load the UI.
On subsequent visits, the core would load, detect that the user has already made a decision, setup the configured apps and stop right there.

To go one step further, there could be another gain by loading the required translations on the fly, instead of bundling them all with the main package.

@felixgirault felixgirault self-assigned this Sep 27, 2021
@felixgirault felixgirault added the enhancement New feature or request label Jan 13, 2022
@felixgirault
Copy link
Contributor Author

I'm closing this issue, as the ongoing work on v3 would solve it (#85)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant