-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Webpack Rebuild Times Over 4000ms - normal? #594
Comments
initial build takes : webpack built 650e4b49ff9ef904ee75 in 11095ms So I think it's normal. But I'm definitely not an expert :) |
Consider changing your devtool to eval. |
Thanks @feesjah and @trueter - I find changing the devtool to 'eval' (in dev.config.js module.exports) drops my recompile from ~4200ms to ~2500ms so definitely makes a big difference, and starts to feel snappy enough to not get in the way of fluid development. I noticed the documentation you linked to mentions the default setting is changing to 'cheap-module-eval-source-map', and I find with 'cheap-module-eval-source-map' I also see recompile times drop to ~2500ms. So maybe this project will want to consider changing the setting in dev.config.js to use the cheap version. I don't know enough about this to understand all of the tradeoffs however. I'll leave this issue open for another day or so in case anyone else wants to comment, then I'll close it. |
Closing since this is a duplicate! |
I am new to this - I've set everything up directly from cloning the repository, and whenever I make a change, Webpack takes over 4000ms to recompile things and update the browser. Is this normal? I saw a reference to people have 300ms build times in a formerly closed issue.
The text was updated successfully, but these errors were encountered: