Call retries were exceeded exception while ng build

Question

I am facing an exception while ng build (generating ES5 bundles for differential loading...)

An unhandled exception occured: Call retires were exceeded

Used versions:

Angular-CLI: 8.3.20
Angular: 8.2.7
Node: 12.12.1

Also in logs, it is mentioned

[error] Error: Call retries were exceeded at ChildProcessWorker.initialize

In tsconfig.app.json if you have `target: es2015` change it with `target: es5` — PierreD, Dec 30 '19 at 13:08
@Angular Can you please tell, why es2015 was causing this exception? — Savan Gadhiya, Dec 31 '19 at 10:56
@TintinSansYeux if we want to use the differential loading we must set the target to es2015 — hosein, Jul 13 '20 at 07:17
This worked for me. I just deleted `node_modules/` and reinstalled. — Schmorrison, Apr 05 '20 at 17:25
its really work just remove node_modules and install again, its working fine — vishal sharma, Jun 25 '20 at 17:01

TmTron · Accepted Answer · 2020-01-10T08:45:17.160

68

Update 10.02.2019

This was a problem of the @angular/cli. Updating the version to >= 8.3.22 should fix the issue: see this comment in #16515

ORIGINAL

Basically the build process is running out of memory: see related angular-cli issues #15493, #16515

The recommended remedy is to:

update node to the latest version e.g. 12.14.0
increase the memory for the build process:
- in your package.json change the "build" script to: node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng build
- in this case the memory is increased to 4GB
  depending on the size of your project you may need more

As a quick workaround it could also work to use older versions of angular/cli and build-angular:

"devDependencies": {
    "@angular-devkit/build-angular": "0.803.20",
    "@angular/cli": "8.3.20",

Another workaround is to disable differential-loading (i.e. skip generation of ES5 bundles), if you want this. Then the build-process will need less memory and may work.

edited Jan 10 '20 at 08:45

answered Jan 01 '20 at 19:41

TmTron

17,012
10
94
142

7

`node --max_old_space_size=4096` did not worked for me. With 8GB it worked. – Jonas Marty Jan 07 '20 at 08:21
I was facing the same issue and it is fixed with above commad - node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng build – purnima kamble Feb 11 '20 at 11:48
only disabling `differential loading` worked for me :( – Obay Abd-Algader Jul 06 '20 at 19:18
It can help if you remove compatibility with older browsers https://angular.io/guide/deployment#differential-loading – nelson6e65 Oct 03 '20 at 16:18
changed to 2048 on my AWS instance with 2GB RAM – works! – Serhii Topolnytskyi Oct 26 '20 at 11:15
1

It has something to do with building the app with "es2015". Using the old target "es5" worked on my side – Zdravko Kolev May 18 '21 at 06:33

score 40 · Answer 2 · answered Jan 04 '20 at 07:05

40

For me editing tsconfig.json resolved my problem.

There was a change in @angular-devkit/build-angular which updated the differential loading. To fix this in your Ionic project, change the target value from “es2015” to “es5” in your tsconfig.json

For more details :- https://forum.ionicframework.com/t/ionic-cordova-build-get-stuck-at-generating-es5-bundles-for-differential-loading/180202/4

answered Jan 04 '20 at 07:05

Aravindh Gopi

2,083
28
36

1

But I need es2015, because es5 fails for @angular/fire 6.0.3 and other. https://github.com/angular/angularfire/issues/2521 – nelson6e65 Oct 03 '20 at 15:54
3

This is not a "solution", just a hack/patch that will have other negative side effects – Richard Apr 28 '21 at 13:45

score 9 · Answer 3 · edited Apr 23 '21 at 10:13

9

Use

node --max_old_space_size=6144 ./node_modules/@angular/cli/bin/ng build

edited Apr 23 '21 at 10:13

Zoe

27,060
21
118
148

answered Apr 06 '21 at 06:20

Kundan Zalte

91
1
1

This works like I charm. For any other beginner like me out there, you replace your build command in package.json with this. – Suyog May 24 '21 at 06:05

score 5 · Answer 4 · answered Apr 06 '21 at 11:25

5

I ran into a similar issue a few days ago.

I was using Node v10 and could only avoid the exceptions during production build by changing to "target": "es5" in tsconfig.json. This removed differential loading, which was undesireable.

However, after updating to Node v14, I no longer get the exceptions and am able to use "target": "es2015" again.

answered Apr 06 '21 at 11:25

Peder

53
1
4

This is the current working solution. thanks! – stoneshishang Apr 27 '22 at 12:40

score 3 · Answer 5 · answered Oct 07 '20 at 11:06

The proposed workarounds above did work for me but there is now a much more elegant solution, tested for Angular9 and above.

No need to mess around manually with the JS heap allocation anymore (node --max_old_space_size=4096...), which most of us are not comfortable with.

The solution is just to add "sideEffects": false to your package.json file.

I found this awesome solution on the official Angular GitHub issues page here and it works smoothly for me.

score 1 · Answer 6 · answered Jan 03 '20 at 03:09

1

I have also met the same issue, by changing the angular/cli version to 8.3.19, the issue has been resolved.

answered Jan 03 '20 at 03:09

john.zhang

11
2

score 0 · Answer 7 · answered May 05 '21 at 11:53

This only applicable for those who have migrated their app to angular 10 and increasing memory also not helping

check your "typescript" and "@types/node" in package.json check whether they are compatible or not in https://www.npmjs.com/package/@types/node

try to downgrade @angular-devkit/build-angular below 0.8XX.X

score 0 · Answer 8 · answered Apr 18 '22 at 11:26

I literally tried everything for days (multiple!) to fix this issue (without increasing the allowed RAM memory on the server, because I was already on the max allowed (shared hosting)). Nothing worked, except for -

--loglevel verbose

I was using it to see what was causing problems. But seems that it takes a lot of memory to show the full log in real-time. After removing this from my commands everything builds from the first try.

score 0 · Answer 9 · answered Aug 08 '23 at 08:26

0

Make sure you are not using older version of Node.

nvm use 16 or greater version works for me!

answered Aug 08 '23 at 08:26

GMKHussain

3,342
1
21
19

score -1 · Answer 10 · answered Jul 06 '21 at 14:39

-1

In my case I upgraded the version of node.

I was running v10.* and I upgraded to v12.20.1 and build was completed.

I use Node Version Manager: nvm for switching versions of node.

answered Jul 06 '21 at 14:39

August

2,045
10
23

score -2 · Answer 11 · edited Apr 18 '22 at 12:33

-2

For react-natives, you can find this helpful.

npm  install --save-dev  escape-string-regexp

edited Apr 18 '22 at 12:33

General Grievance

4,555
31
31
45

answered Sep 01 '21 at 10:52

Mubaraka Mubahood

229
2
9

Call retries were exceeded exception while ng build

11 Answers11

Update 10.02.2019

ORIGINAL

Linked