speed-measure-webpack-plugin
speed-measure-webpack-plugin copied to clipboard
stephencookdev
general output time and modules with no loaders
during start i can see that modules with no loaders is the most expensive part but i have no more detail about that, which are the modules without loader?:
SMP ⏱
General output time took 31.27 secs
SMP ⏱ Plugins
Object took 0.016 secs
ProvidePlugin took 0.001 secs
SMP ⏱ Loaders
modules with no loaders took 15.96 secs
module count = 6838
babel-loader took 4.42 secs
module count = 107
css-loader took 2.26 secs
module count = 16
underscore-template-loader took 1.11 secs
module count = 24
json-loader took 0.636 secs
module count = 2
file-loader took 0.151 secs
module count = 11
style-loader, and
css-loader took 0.012 secs
module count = 5
during reload my worst loading time comes from general output time:
SMP ⏱
General output time took 6.079 secs
SMP ⏱ Plugins
Object took 0.005 secs
ProvidePlugin took 0 secs
SMP ⏱ Loaders
babel-loader took 0.294 secs
module count = 1
what does it mean? is it the time spent to compile my own code? how can i figure out the optimization for this?
Hey :smile: Sorry for the very late response
"modules without loaders" basically just means vanilla JS files, which webpack can handle out of the box.
As for the "general output time" on the reload, this tends to be generally down to webpack reading in from the file-system, but it's hard to say - it'll be very repo specific!
Where would you all look for information on this? Would a link to a README doc or something, just under the "modules with no loaders" description?
@daton89 Try playing with the devtool property, set it eval to see if you see any significant change, if so read Webpack's docs and try the other, less cheap, options
@daton89 Try playing with the
devtoolproperty, set itevalto see if you see any significant change, if so read Webpack's docs and try the other, less cheap, options
this is insane!!! this made a significant change! but why?? 💯
