-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
npm run build takes 1-2 hours to build #4785
Comments
Can you disable sourcemaps? Put
in your Also it would help to have more info about |
Thanks @gaearon for the really quick reply "react": "^16.3.2", And here is my complete package.js : https://gist.github.com/clu3/d008f57f77dbff284427aa4666fb3b58 Im trying to re-build with no source map. It still looks like it's taking time. So i'll go ahead and post my comment here, hoping i'll get something figured out earlier. Update |
This application sounds massive! With source maps disabled, there's no way we're going to squeeze more performance out of your build unless if you upgrade to the new alpha and give it a try -- it has a lot of caching on by default, but be aware it has its own set of bugs/issues which causes suboptimal bundle distribution. Stay tuned! |
First off, thank you for everything.
I have a fairly big react app (200K locs , css excluded), and recently it takes me hours to npm run build (It used to be like 9min which was aweful as well but i could still live with it). Some change in the last few weeks, which we haven't been able to identify what because our package.json still looks fine, has increased the build time from 10m to 1-2hours, sometimes 3 on my laptop. And the build process usually runs out of memory and dies on my colleagues' machines.
We use react-router and react-loadable to split the code.
When I examine the build folder, i still have like
main.ad2ec57c.js 3.5M
main.ad2ec57c.js.map : 21M
and lots of other chunks of size 5-100K.
Can you pls point me some direction on how to go about solving this?
The text was updated successfully, but these errors were encountered: