[Bug] CircleCI + Terser Error: Call retries were exceeded
See original GitHub issueBug
When you use CircleCI to build the project, it will sometimes not compile throwing the error below.
Looks like this is a known problem here: https://github.com/webpack-contrib/terser-webpack-plugin/issues/143#issuecomment-573954013. Recommend setting the webpack configuration based on the feedback.
#!/bin/bash -eo pipefail
yarn build
yarn run v1.21.1
$ react-scripts build
Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run next command `yarn upgrade`
Failed to compile.
Failed to minify the bundle. Error: static/js/1.dc6042b5.chunk.js from Terser
Error: Call retries were exceeded
at /home/circleci/project/node_modules/react-scripts/scripts/build.js:196:23
at finalCallback (/home/circleci/project/node_modules/webpack/lib/Compiler.js:257:39)
at /home/circleci/project/node_modules/webpack/lib/Compiler.js:273:13
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/circleci/project/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:22:1)
at AsyncSeriesHook.lazyCompileHook (/home/circleci/project/node_modules/tapable/lib/Hook.js:154:20)
at onCompiled (/home/circleci/project/node_modules/webpack/lib/Compiler.js:271:21)
at /home/circleci/project/node_modules/webpack/lib/Compiler.js:681:15
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/circleci/project/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:4:1)
at AsyncSeriesHook.lazyCompileHook (/home/circleci/project/node_modules/tapable/lib/Hook.js:154:20)
at /home/circleci/project/node_modules/webpack/lib/Compiler.js:678:31
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/circleci/project/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:4:1)
at AsyncSeriesHook.lazyCompileHook (/home/circleci/project/node_modules/tapable/lib/Hook.js:154:20)
at /home/circleci/project/node_modules/webpack/lib/Compilation.js:1423:35
at AsyncSeriesHook.eval [as callAsync] (eval at create (/home/circleci/project/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:4:1)
at AsyncSeriesHook.lazyCompileHook (/home/circleci/project/node_modules/tapable/lib/Hook.js:154:20)
at /home/circleci/project/node_modules/webpack/lib/Compilation.js:1414:32
Read more here: https://bit.ly/CRA-build-minify
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Exited with code exit status 1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:90
- Comments:50 (8 by maintainers)
Top Results From Across the Web
Resolving "Failed to minify the bundle" Errors - CircleCI Support
TerserWebpackPlugin The following error message is usually related to running out of ... from Terser Error: Call retries were exceeded.
Read more >nuxt js - terser - Call retries were exceeded - Stack Overflow
This issue appears when bundle size has increased and there is not enough memory to build the project. I faced similar issue and...
Read more >Paul Grau on Twitter: "The fix (which took me an hour to find) seems ...
Its dependencies are always out of date, it's impossible to configure... now ... [Bug] CircleCI + Terser Error: Call retries were exceeded ·...
Read more >terser-webpack-plugin - npm.io
Using Webpack v4, you have to install terser-webpack-plugin v4. ... explicitly number of CPUs to avoid Error: Call retries were exceeded (see #143,...
Read more >TerserWebpackPlugin | webpack 中文文档
webpack v5 开箱即带有最新版本的 terser-webpack-plugin 。 ... 环境,则需要显式设置CPU 数量,以避免 Error: Call retries were exceeded (请参阅#143,#202 )。
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Activity
I think that this issue still exists.