Maximum call stack size exceeded on npm install

Question

I'm trying to run npm install, this is output from console:

npm ERR! Linux 4.8.0-27-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8

npm ERR! Maximum call stack size exceeded
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

and this is content of npm-debug.log:

113791 verbose stack RangeError: Maximum call stack size exceeded
113791 verbose stack     at Object.color (/usr/lib/node_modules/npm/node_modules/npmlog/node_modules/console-control-strings/index.js:115:32)
113791 verbose stack     at EventEmitter.log._format (/usr/lib/node_modules/npm/node_modules/npmlog/log.js:252:51)
113791 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npmlog/log.js:138:24)
113791 verbose stack     at emitThree (events.js:116:13)
113791 verbose stack     at emit (events.js:194:7)
113791 verbose stack     at .<anonymous> (/usr/lib/node_modules/npm/node_modules/npmlog/node_modules/are-we-there-yet/tracker-group.js:23:18)
113791 verbose stack     at emitThree (events.js:116:13)
113791 verbose stack     at emit (events.js:194:7)
113791 verbose stack     at .<anonymous> (/usr/lib/node_modules/npm/node_modules/npmlog/node_modules/are-we-there-yet/tracker-group.js:23:18)
113791 verbose stack     at emitThree (events.js:116:13)
113791 verbose stack     at emit (events.js:194:7)
113792 verbose cwd /home/giorgi/AdMove/dev/web-advertiser-admove
113793 error Linux 4.8.0-27-generic
113794 error argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
113795 error node v6.9.1
113796 error npm  v3.10.8
113797 error Maximum call stack size exceeded
113798 error If you need help, you may report this error at:
113798 error     <https://github.com/npm/npm/issues>
113799 verbose exit [ 1, true ]

Removed node_modules several times and tried to reinstall. Can't understand what's the reason that causes this and how to fix it.

First of all, I'd check the github issues link for similar problems, and add it if it's not a known problem. Also, why are you trying to install v4.2.6? The current latest build is v7.1.0, and the recommended stable build is v6.9.1. Clear everything out, try 6.9.1, and update the question. — TheEnvironmentalist, Nov 12 '16 at 18:44
Updated to v6.9.1 still got same error and updated question also. Thanks anyway [TheEnvironmentalist](http://stackoverflow.com/users/2480092/theenvironmentalist) — GROX13, Nov 12 '16 at 18:58
Some advice around here https://github.com/npm/npm/issues/10776 — Boris Charpentier, Nov 12 '16 at 19:11
im my case, this was caused due to a recursive declaraion in package.json ;) — Alberto S., Mar 06 '20 at 09:14
in my case, it was caused because I had lost internet connection — RayJ_inSJ, May 15 '20 at 21:07

score 142 · Answer 1 · edited Feb 06 '19 at 00:00

142

metzelder's answer helped me fix the issue. however if you run the command npm cache clean, it will give you a message

As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid

So, as of npm5 you can do by adding a --force flag to the command.

So the command is:

npm cache clean --force

edited Feb 06 '19 at 00:00

G-Ram

23
3
6

answered Jul 14 '18 at 08:06

kuntam robo

1,831
1
9
12

246

I sure hope you know what you are doing. – CloudMeta Feb 20 '19 at 23:51
On a *Node v10.15.1* and *npm 6.4.1* environment this worked like a charm! Thanks a lot. – MulleOne Apr 23 '19 at 11:15
3

As for me I had move the current working directory to another folder – seems like it mixed up npm. Deleting node_modules and reinstalling did the trick – Philippe Hebert Jun 11 '19 at 21:42
13

@MetaGuru please explain what are the consequences of running this command... – cdalxndr Mar 03 '20 at 16:28
@cdalxndr it's a joke since that's what the command says when you use the `--force` flag. ie: `npm WARN using --force I sure hope you know what you are doing.` – CTS_AE Apr 20 '20 at 12:35
3

@CTS_AE I don't think the npm team added that message as a joke. There must be a consequence and someone should explain it. – cdalxndr Apr 20 '20 at 15:45
2

@cdalxndr I was saying that it is left as a comment as a joke/satire, as a direct quote from `npm` he wasn't really adding anything helpful, but more of a meme at this point. You can read more about the actual command here: https://docs.npmjs.com/cli-commands/cache.html it explicitly explains what force does; that all cache items are now fully verified for their integrity, if something is corrupt it will self heal, thus the cache should always be in a proper state and never cleared unless you're trying to reclaim disk space, thus you will need to append `--force`. Note: May vary per version. – CTS_AE Apr 20 '20 at 21:45
1

TLDR; it will actually delete the cache like it's supposed to. Later dependency installs might go slower until re-cached. – CTS_AE Apr 20 '20 at 22:03
Seems I had to do an update to npm with `npm i -g npm` then run this `npm cache clean --force` now I can finally run `npm i` – CTS_AE Apr 20 '20 at 22:07
npm suggests running `npm install --cache /tmp/empty-cache` to run with a temporary empty cache rather than deleting the real one. I would try this to see if it solves the problem before running `npm cache clean --force` – kat Apr 23 '21 at 13:57

score 120 · Answer 2 · edited Sep 26 '19 at 01:41

120

npm rebuild it has solved my problem

edited Sep 26 '19 at 01:41

João Marcos Gris

71
8

answered Nov 07 '18 at 06:51

YYY

3,102
4
16
20

41

Can anyone explain this answer further? Why does this solve the problem? – Patrick Szalapski Mar 27 '19 at 13:02
4

deleted package-lock.json and npm rebuild did the trick for me – Meet Patel Aug 08 '19 at 10:07
in my case, certain files in my .npm folder were installed as root. npm cache verify tells you what is wrong. – kirenpillay Nov 17 '19 at 07:34
This did the trick. npm cache clean did not work on this occasion. – Shiva Naru Jun 01 '20 at 19:26
1

from the official docs: > This command runs the npm build command on the matched folders. This is useful when you install a new version of node, and must recompile all your C++ addons with the new binary. – vivekmore Oct 10 '20 at 12:08
This did work for me. Thanks. Note - However, you need to be very sure about the cache force clean. – Tethys0 Dec 12 '20 at 12:34

score 74 · Answer 3 · edited Dec 14 '20 at 20:16

74

Try removing package-lock.json and the node_modules folder:

rm package-lock.json
rm -r node_modules

edited Dec 14 '20 at 20:16

bobbyz

4,388
3
27
41

answered Apr 06 '19 at 17:37

Марат Зимнуров

982
5
12

18

You're killing the purpose of package-lock.json if you delete it. It guarantees that your dependencies will be deterministic. – Eliseu Monar dos Santos Aug 12 '19 at 02:16
11

True, but if you can't install your app on say a different platform, then you have no choice but to do this. – Marc Oct 12 '19 at 07:42
3

`npm install` should restore the `package-lock.json` file anyway – kip2 Sep 03 '20 at 20:46
FWIW, these commands should be run inside your `functions` folder. I made the mistake of running it in the root folder – kip2 Oct 15 '20 at 11:04
2

@kip2 It will produce a new `package-lock.json`, but not necessarily the same one as new versions of dependencies may be available since it was last created. It's possible that one of these new versions could break things. – Michael Mior Dec 14 '20 at 20:24
@kip2 where can we read about `functions` folder, never heard of it :) – Maxim V. Pavlov Mar 07 '21 at 11:44
@MaximV.Pavlov here's the link: https://firebase.google.com/docs/functions/manage-functions#deploy_functions. In particular, note: _By default, the Firebase CLI looks in the functions/ folder for the source code. You can specify another folder by adding the following lines in firebase.json_: "functions": { "source": "another-folder" } – kip2 Mar 08 '21 at 03:32

score 22 · Answer 4 · edited Nov 19 '18 at 20:21

22

I had the same issue with npm install. After a lot of search, I found out that removing your .npmrc file or its content (found at %USERPROFILE%/.npmrc), will solve this issue. This worked for me.

edited Nov 19 '18 at 20:21

Rene Knop

1,563
3
12
24

answered Nov 19 '18 at 19:37

Arwa S k

246
2
7

score 20 · Answer 5 · edited Dec 14 '20 at 20:25

20

npm uninstall

npm cache clean --force

I tried these two methods but they didn't work. After, I deleted the node_modules directory and ran npm install again, it still didn't work. Lastly, I deleted package-lock.json and created a new package-lock.json file using

npm install

edited Dec 14 '20 at 20:25

Michael Mior

26,133
8
80
110

answered Feb 18 '19 at 11:24

Kerim Kuşcu

339
2
11

5

Deleting the package-lock.json file fixed it for me, Thanks! – Ryan Wilson Mar 21 '19 at 15:57
I sure hope you know what you are doing. – Ibrahim shamma Feb 20 '21 at 09:02
You don't have to do. @Ibrahimshamma – Kerim Kuşcu Feb 22 '21 at 07:25

score 15 · Answer 6 · edited May 15 '19 at 06:51

15

I have overcome this issue by doing following:

Delete all the content of the npm dependencies. You can find the default install location according to this thread: https://stackoverflow.com/a/5926706/1850297
Before you run npm install command, I suggest to run npm cache clean --force

edited May 15 '19 at 06:51

Kesav Sundar M

127
7

answered Apr 10 '18 at 09:45

metzelder

504
1
11
32

Message from `npm cache clean`: "As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid." – Ian Grainger Jul 03 '18 at 08:57

score 12 · Answer 7 · answered Aug 15 '19 at 14:41

12

In my case, update to the newest version:

npm install -g npm

answered Aug 15 '19 at 14:41

AvantContra

331
1
3
10

Gopi P · Answer 8 · 2020-11-04T05:44:25.770

12

npm rebuild will work for sure

edited Nov 04 '20 at 05:44

answered Oct 12 '19 at 03:38

Gopi P

381
5
15

score 10 · Answer 9 · answered Oct 27 '18 at 15:00

10

I deleted

node_modules

and then reinstalled by

npm install

It worked for me

answered Oct 27 '18 at 15:00

Umair Khalid

1,961
1
18
25

3

funny enough i had to restart ,my computer in addition to your steps for it to work, since i am working with wsl – Avshalom Nov 18 '19 at 12:44
This worked for me, but none of the other solutions did – Code Whisperer Aug 18 '20 at 11:09

score 7 · Answer 10 · answered Aug 03 '20 at 16:37

I have also faced the same problem and this is how i resolved it.

First of all you need to make sure that your node and npm versions are up to date. if not please upgrade your node and npm packages to latest versions.
```
nvm install 12.18.3 // update node version through node version manager

npm install npm // update your npm version to latest
```
Delete your node_modules folder and package-lock.json file.
Force clean the entire NPM cache by using following comand.
```
npm cache clean --force
```
Re-Install all the dependencies.
```
npm install
```
If above step didn't resolve your problem, try to re-install your dependencies after executing following command.
```
npm rebuild
```

I am unable to delete node_modules. I've had this occur twice. First time I had to `npm eject`, but I still had a few folders I could never remove `common-tags`, `react-dev-utils`, and `stream-browserify`. — Inarus Lynx, Mar 18 '21 at 13:03

score 6 · Answer 11 · answered Dec 26 '19 at 13:57

6

This issue can also happen if you're trying to install a package that doesn't exist or if you're trying to install a version that doesn't exist.

answered Dec 26 '19 at 13:57

Melchia

16,699
16
70
93

score 5 · Answer 12 · edited Aug 26 '20 at 04:53

npm cache clean returns below message

As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead. On the other hand, if you're debugging an issue with the installer, you can use npm install --cache /tmp/empty-cache to use a temporary cache instead of nuking the actual one.

If you run npm cache verify, as specified above, then it actually runs cache verification and garbage collection which fixes the problem.

Cache verified and compressed (~\AppData\Roaming\npm-cache_cacache): Content verified: 6183 (447214684 bytes) Content garbage-collected: 16 (653745 bytes) Index entries: 9633

This was enough for me. npm cache verify fixed the issue in a way that removing node_modules didn't. (And I wasn't going to nuke the cache or package-lock.json). Pretty sure this is an issue with npm, though. Can't see why npm cache verify would change anything if it truly did self-heal. — Stuart Watt, Mar 05 '20 at 15:19

naorz · Answer 13 · 2019-09-19T10:46:54.690

I'm not a Windows user, so if you are, try to check Rene Knop comment.

For Unix/OSX users, I've removed the root .npmrc file ~/.npmrc.
Before you're going to try it, please, check if there is nothing necessary over there you can use this command to bring all content into your terminal: cat ~/.npmrc .

If you have got something like:

cat: /Users/$USER/.npmrc: No such file or directory

to save a copy:

cp ~/.npmrc ~/.npmrc_copy

Now, try to remove it (Works for bash users: Unix / Ubuntu / OSX ...):

rm -f ~/.npmrc

This worked for me.
Hope this will be helpful for others.

danieltan95 · Answer 14 · 2020-11-14T15:18:31.613

3

Happened in docker (node:15-buster) for me.

Remember to use WORKDIR /<folder> so that it doesn't conflict with original npm libraries installed.

The folder can be anything but system folders, so that includes using /.

edited Nov 14 '20 at 15:18

answered Oct 30 '20 at 08:29

danieltan95

549
5
9

I had the "call stack size exceeded" issue in docker until I moved the WORKDIR line to near the top of the Dockerfile. Apparently the location of that line matters. – zipzit Nov 07 '20 at 07:53
I had `WORKDIR /` at the top but it seems doing an `npm i` or `npm ci` from `/` blows things up. – Paul Robello Nov 13 '20 at 01:24
@PaulRobello yep, the folder has to be separate from the original, lemme edit the answer to be clearer. – danieltan95 Nov 14 '20 at 15:18

Gajendra K S · Answer 15 · 2019-02-17T08:24:14.713

2

You uninstall npm package and force clean the cache and close terminal and reinstall whichever package be.

$sudo npm uninstall <package - name>
$sudo npm cache clean --force

Then restart terminal and check

Still not working upgrade both npm and node to the latest version

edited Feb 17 '19 at 08:24

answered Feb 17 '19 at 07:53

Gajendra K S

57
5

score 2 · Answer 16 · edited Dec 14 '20 at 20:27

2

In case none of these answer work for you, it may be because the terminal you're using isn't the right one/ your node_modules is used by another part of your computer.

In my case I kept juggling between this error (maximum call stack size exceeded) and the access error event when I did a sudo npm i.

The fix was to close my IDE (which was WebStorm), run npm i in a basic terminal, and that was it.

edited Dec 14 '20 at 20:27

Michael Mior

26,133
8
80
110

answered May 14 '19 at 10:33

Jonathan Simonney

399
1
6
20

Closing the editor fixed it for me. (Netbeans for me) – Wim Pruiksma Apr 29 '20 at 14:51

score 2 · Answer 17 · answered Nov 16 '19 at 10:15

I also had the same problem. I had tried the previous solutions, but the solution for me was much simpler. I only had to remove the space in the directory and then run npm i again

Thanks to: https://github.com/nodejs/node-gyp/issues/809#issuecomment-155019383 for pointing this out.

score 1 · Answer 18 · answered Nov 06 '18 at 13:33

I tried everything to fix this issue on my Mac. I think the issue started when I had already downloaded npm from Node.js and then reinstalled it with Homebrew while following along with a Team Treehouse video.

Here's what I tried:

From https://docs.npmjs.com/misc/removing-npm

sudo npm uninstall npm -g
sudo make uninstall
sudo rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm*

From How do I completely uninstall Node.js, and reinstall from beginning (Mac OS X)

sudo rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/{npm*,node*,man1/node*}

Here's what worked:

In the end, the only thing that worked for me was to clone down the npm-reinstall repo from GitHub that completely removed everything related to npm on my Mac.

https://github.com/brock/node-reinstall

I then had to reinstall node and npm from Node.js.

Rajashekhar Reddy · Answer 19 · 2019-05-16T10:50:40.113

1

I tried everything to fix this issue on my windows 7 machine like

Reinstalling and rebuilding npm

At last, I fixed this small configuration setting issue by wasting my entire day.

How I resolved this issue

Removing my project specific configurations in global .npmrc at location like drive:/Windows/Users/../.npmrc

edited May 16 '19 at 10:50

answered May 16 '19 at 10:42

Rajashekhar Reddy

77
4

score 1 · Answer 20 · answered Nov 01 '19 at 12:47

1

I solved it 100% I had this problem with gulp version: 3.5.6.

You should clean the package-lock.js and then run npm install and It worked form

answered Nov 01 '19 at 12:47

Hidayat Arghandabi

154
2
12

score 1 · Answer 21 · answered Jan 07 '20 at 16:18

Our company dev environment uses Artifactory as the default registry for our NPM dependencies, and when running npm install it was defaulting to this, which did not work... so manually specifying the main npm registry via npm install --registry https://registry.npmjs.org fixed this issue for me...

score 1 · Answer 22 · answered Jun 10 '20 at 03:58

I was facing the same error, I was trying to install jest into to one of the packages in a monorepo project.

If you are using Yarn + Learna to package a monorepo project, you will have to navigate to the package.json inside the target package and then run npm install or npm install <package name>.

score 1 · Answer 23 · answered Nov 02 '20 at 11:18

In general, once a module has been installed, it's much more convenient to use npm ci instead of npm install. Please check out this SO answer for the advantages of the former with respect to the later in a production environment. So please just run

npm ci

All dependencies will be updated, and the problem will disappear. Or it will error in the case there's some grave de-synchronization between one and the other.

score 0 · Answer 24 · answered Feb 15 '19 at 23:09

0

I had this problem and it was due to an upgrade of my git executable. I rolled back to Git-2.21.0.rc1.windows.1-64-bit and added this to my environment path and it fixed my issue.

answered Feb 15 '19 at 23:09

Finchy70

361
4
22

score 0 · Answer 25 · answered Jul 30 '19 at 18:12

The one thing that finally worked for me on Mac was upgrading from node 8.12 to 10.x using NVM.

I uninstalled all other versions of Node with NVM, then installed 10.x, then ran nvm alias default node, which tells NVM to always default to the latest available node version on a shell.

After that, my live reloading issue went away!

score 0 · Answer 26 · answered Oct 17 '19 at 20:33

0

Switching to yarn solved the issue for me.

answered Oct 17 '19 at 20:33

vgaltes

890
9
15

score 0 · Answer 27 · answered Jan 10 '20 at 17:48

0

For those having this issue when building a Docker image with Jenkins (or any CI), make sure the package-lock.json is also copied to the container.

COPY ./src/package*.json /home/node/
RUN npm install

For us, the install actually went fine, the error only occurred when running npm prune production for the production image.

answered Jan 10 '20 at 17:48

Adam Eri

673
4
12

I have this problem with npm prune and NODE_ENV not set to production. Solved by removing node_modules and npm install again – Eduardo Mar 12 '20 at 23:21

score 0 · Answer 28 · answered Jan 29 '20 at 23:22

If your default npm registry is something other than the public npm repository (you can check this by going to your .npmrc file or checking your npm config via npm CLI commands), you could try unsetting the registry config so it points back to the public npm repository. Then run npm install again.

If you have dependencies that aren't available in the public npm repository, try temporarily removing those dependencies from package.json. This will allow you to run npm install. Finally, revert the dependencies and registry config you removed and run npm install one last time to install the rest of your dependencies.

score 0 · Answer 29 · answered Apr 08 '20 at 14:38

0

Today we encountered this error when running an npm prune even after running an npm cache clean --force.

Versions:

node 13.8.0 
npm 6.13.6

Deleting the package-lock.json worked for this case as well. Thank you all!

answered Apr 08 '20 at 14:38

Jeff Hampton

46
3

nishant · Answer 30 · 2020-06-19T22:36:13.153

0

I was facing a similar error. I tracked it down to the fact that npm was unable to delete files from the .bin folders for a npm link'd folder. So I went in and rm -rf all the .bin folders from the npm link'd folder.

find "linked-folder" -type d -name ".bin" -print  
For all folders listed | rm -rf

That resolved the issue.

edited Jun 19 '20 at 22:36

answered Jun 19 '20 at 22:15

nishant

526
1
8
18

score 0 · Answer 31 · answered Jul 20 '20 at 06:17

0

Following steps helped me to solve this issue:

Stop all react strips (e.g. start build)
run npm cache clean --force
run npm install

answered Jul 20 '20 at 06:17

ATQSHL

181
1
8

score 0 · Answer 32 · answered Jul 20 '20 at 15:28

0

echo 65536 | sudo tee -a /proc/sys/fs/inotify/max_user_watches

works for me on Ubuntu.

answered Jul 20 '20 at 15:28

Dionis Oros

455
5
8

score 0 · Answer 33 · answered Jul 26 '20 at 23:21

0

npm cache clean --force

This works for me with node 8, and npm 6+

answered Jul 26 '20 at 23:21

thedarkgriffen

326
3
16

score 0 · Answer 34 · answered Sep 08 '20 at 15:28

The error message may not be directly related to the npm procedure you are trying to run, it might be other node processes running that conflict or use up resources.

In my case I had an empty node_modules folder fresh from a recent init and still got

npm ERR! Maximum call stack size exceeded

when running npm install --save-dev @wordpress/scripts for WordPress plugin development.

The issue was a live reload watcher running in my wp-content folder, with that stopped the install worked first time.

score 0 · Answer 35 · answered Sep 10 '20 at 14:29

In my case Maximum call stack size exceeded was triggered by another error earlier. The logs looked like this:

// ... skipping some deprecation warnings

> core-js@3.6.5 postinstall /root/.nvm/versions/node/v14.10.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-graphql-types-generator/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

sh: 1: node: Permission denied
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/@aws-amplify/cli/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! Maximum call stack size exceeded

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-09-10T14_10_28_397Z-debug.log

Note sh: 1: node: Permission denied that led me to https://forum.vuejs.org/t/cannot-install-vue-cli-permission-error-in-require-postinstall/82017/7

I had to add --unsafe-perm to the install command and run it as root:

sudo npm install -g --unsafe-perm @aws-amplify/cli

It works for me with I am using npm on Windows WSL subsystem. `npm install --unsafe-perm` — Dylan, Oct 16 '20 at 18:47

score 0 · Answer 36 · answered Nov 26 '20 at 20:14

I had this problem and it turned out, I had a symbolic link inside node_modules pointing to it's parent, i.e.

[user@localhost]$ ls -la /path/to/project/node_modules
total 3272
...
lrwxrwxrwx   1 user user  50 Nov 26 18:38 node_modules -> ../node_modules
...

I mean, somehow I messed the bash script and it created a circular symbolic link. Removing the symbolic link solved the issue.

score 0 · Answer 37 · answered Dec 05 '20 at 20:35

0

rm -rf node_modules

and then reinstall worked for me.

_{note: probably don't need to rip out your lock files}

answered Dec 05 '20 at 20:35

Xlee

3,543
1
19
35

score 0 · Answer 38 · answered Mar 17 '21 at 12:03

0

Most of the times, this issue occurs if you are using the system provided by the organization you work for and it's vpn restricts the use of this command. In this case, you may try to disconnect from organization vpn and then execute this command.

answered Mar 17 '21 at 12:03

jaihind

735
1
6
9

score -1 · Answer 39 · answered Jun 21 '20 at 06:31

I came across to same problem but in my case I have been using yarn from beginning but from some package readme I copied the npm install command and got this error. Later realised that yarn add <package-name> solved the issue and package was installed.

It might help someone in future.

score -1 · Answer 40 · answered Dec 14 '20 at 13:45

-1

This problem is solved by clearing npm cache and then install re-install npm packages, so to solve this

Run clean the cache

npm cache clean --force

Then This stage is very important

npm rebuild

Finally re-install node modules

npm install

Good Luck

answered Dec 14 '20 at 13:45

Crispen Gari

1,343
9
12

score -1 · Answer 41 · answered Apr 15 '21 at 10:13

Try this first!

Run npm install again

Crazily simple, but I don't know who else tried this so thought I should put it up here, despite all the existing answers. I suggest people try this first though, given it's the simplest solution and doesn't come with the risks others have noted when, say, deleting package-lock.json

Theory:

This is totally unproven as I'm just doing this to run a code screen (i.e. a totally new repo to me) and I guessed that some of the packages had been installed the first time npm install was run; it just ran out of resources later on.

I guessed that if I ran npm install again it would skip the install of the now-installed packages and complete, or at least get further. The behaviour I guessed at was what I saw but I didn't actually debug or test if this behaviour was for the reasons I guessed!

Clearly a lot of different things have worked for different people, but I thought I should add an answer to this already well-answered question on the basis it's the most trivial to do.

And if you're lucky it's going to run for long enough for you to grab a or ☕

Maximum call stack size exceeded on npm install

41 Answers41

Here's what I tried:

Here's what worked:

How I resolved this issue

Try this first!

Theory:

Linked

Related