Closed dominikj111 closed 3 years ago
Bot Hey Leute Checkt auf jeden Fall @Tomato ab und seine Coolen Bots
Server : https://discord.gg/3ep6e3vEJf
Website : https://x10-gaming.eu/service/dc
sudo npm cache clean --force
this command helped me
It doesn't work ... @designervoid I raised a question here also.
Same for us. I also commented on SO on the issue. For us its 100% reproducible. It works with npm7 and also with yarn. Also on all macs that previously to BigSur updates ran node + npm 6. All new macs broken though. (at least 3 colleges)
We cannot find any difference on the setup though. Also (as described on @domino2 SO post here https://stackoverflow.com/questions/65286917/cant-install-npm-packages-anymore-due-to-macos-big-sur-upgrade its not working inside a docker container either if on a mounted volume.
npm v6
is no longer in active development; We will continue to push security releases to v6
at our team's discretion as-per our Support Policy.
If your bug is preproducible on v7
, please re-file this issue using our new issue template.
If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo
Current Behavior:
Whenever I'll
npm install
it end with the message Maximum call stack size exceeded.Expected Behavior:
It will finish as usual.
Steps To Reproduce:
Not sure as I'm only one in the team as far as I know.
Environment:
ProductName: macOS ProductVersion: 11.0.1 Darwin: 20.1.0 nodejs: v14.15.1 npm: v6.14.8
The problem is with any possible installation of node/npm except version npm v7.
Also whenever I ran
npm install
in the docker environment (ubuntu:focal) or virtualbox (Windows 10), it failed in case that this command was running upon shared folder. When I copied the project folder "into" the virtual drive environment (not shared/not mapped from host to docker container) it passed.I also described that issue in the stackoverflow.com.
I tried to build the npm from source on dockerized ubuntu:focal upon the mapped folder and got slightly different error.