-
Notifications
You must be signed in to change notification settings - Fork 76
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
Optimize bundles sizes, add csso, fix lighthouse issues #252
Comments
We need to divide the assets per-module again, so they are not loaded in the bundle if not needed. |
Seems impossible in the current state of PrestaShop |
Why not? It's all about putting proper css to proper directories: You can even unregister a default asset by putting an empty file there: And we should be able to specify what we want to load on which controller by specifiying it in theme.yml: |
CSS files path depends on the module developer choice: some are inside We have absolutely no way to make this automatic And we absolutely have no way to add our own stylesheets depending on the fact that a module is activated and installed inside the current page we're visiting. Yes, we can register some stylesheets depending on the controller we are, but modules can be moved into different hooks, it's not a reliable way to do this, except for the core styles of the page |
Yes, but at least the module CSS will be loaded only on pages where it's needed, not everywhere. |
With the way hummingbird is written now, all JS, all CSS, for all modules (even uninstalled) are loaded absolutely everywhere. |
Yeah I know, we can improve it and it's almost ready: NeOMakinG@d570e8b But we can't do it perfectly for sure :( |
@Oksydan wants to take this subject, I'll move it to WIP |
Assign me 👀 |
No description provided.
The text was updated successfully, but these errors were encountered: