-
Notifications
You must be signed in to change notification settings - Fork 80
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
Optimising modules with no loaders #43
Comments
Hey @ersel :) So "modules with no loaders" are any JS file that webpack just loads in. Probably your bulk of files here is coming from I'll try and add a feature in the future to help visualise what all of these files are that are taking time. But until then, if you download webpack-bundle-analyzer you should be able to see all of your dependencies (sorted by their size). Cutting down on needlessly large dependencies will help reduce this number! |
Thanks Steve, a list of files would be very helpful to see. I will try webpack-bundle-analyzer. Maybe CLI could even give some recommendations on how to optimize different loaders. e.g: |
Hello, has this function been implemented, and is there any documentation? |
Hi @stephencookdev ,
Firstly, thanks for developing this plugin. I have a question regarding the
Modules with no loaders
output.Our current webpack config produces the following output:
I was wondering if and how we can optimize our configuration to skip those 104 modules with no loaders?
The text was updated successfully, but these errors were encountered: