npm install -g always give me Maximum call stack size exceeded


(Sherwin) #1

I use last version npm version(6.4.1) on windows 10.

I try to install webpack, but get error:

npm install -g webpack
npm ERR! Maximum call stack size exceeded

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\lus2\AppData\Roaming\npm-cache_logs\2019-02-18T05_01_04_511Z-debug.log

the log is:

Blockquote

8 http fetch GET 200 https://registry.npmjs.org/acorn-dynamic-import 207ms
29 silly pacote range manifest for enhanced-resolve@^4.1.0 fetched in 209ms
30 silly resolveWithNewModule enhanced-resolve@4.1.0 checking installable status
31 silly pacote version manifest for @webassemblyjs/helper-module-context@1.8.2 fetched in 217ms
32 silly resolveWithNewModule @webassemblyjs/helper-module-context@1.8.2 checking installable status
33 silly pacote range manifest for acorn@^6.0.5 fetched in 218ms
34 silly resolveWithNewModule acorn@6.1.0 checking installable status
35 http fetch GET 200 hxxps://registry.npmjs.org/eslint-scope 70ms
36 silly pacote range manifest for acorn-dynamic-import@^4.0.0 fetched in 228ms
37 silly resolveWithNewModule acorn-dynamic-import@4.0.0 checking installable status
38 silly pacote version manifest for @webassemblyjs/ast@1.8.2 fetched in 232ms
39 silly resolveWithNewModule @webassemblyjs/ast@1.8.2 checking installable status
40 silly pacote version manifest for @webassemblyjs/wasm-edit@1.8.2 fetched in 231ms
41 silly resolveWithNewModule @webassemblyjs/wasm-edit@1.8.2 checking installable status
42 silly pacote range manifest for eslint-scope@^4.0.0 fetched in 86ms
43 silly resolveWithNewModule eslint-scope@4.0.0 checking installable status
44 http fetch GET 200 hxxps://registry.npmjs.org/json-parse-better-errors 69ms
45 http fetch GET 200 hxxps://registry.npmjs.org/ajv 241ms
46 silly pacote range manifest for json-parse-better-errors@^1.0.2 fetched in 81ms
47 silly resolveWithNewModule json-parse-better-errors@1.0.2 checking installable status
48 silly pacote range manifest for ajv@^6.1.0 fetched in 254ms
49 silly resolveWithNewModule ajv@6.9.1 checking installable status
50 http fetch GET 200 hxxps://registry.npmjs.org/loader-utils 69ms
51 http fetch GET 200 hxxps://registry.npmjs.org/loader-runner 75ms
52 http fetch GET 200 hxxps://registry.npmjs.org/memory-fs 70ms
53 http fetch GET 200 hxxps://registry.npmjs.org/micromatch 74ms
54 silly pacote range manifest for loader-utils@^1.1.0 fetched in 86ms
55 silly resolveWithNewModule loader-utils@1.2.3 checking installable status
56 http fetch GET 200 hxxps://registry.npmjs.org/mkdirp 75ms
57 silly pacote range manifest for loader-runner@^2.3.0 fetched in 94ms
58 silly resolveWithNewModule loader-runner@2.4.0 checking installable status
59 silly pacote range manifest for memory-fs@~0.4.1 fetched in 94ms
60 silly resolveWithNewModule memory-fs@0.4.1 checking installable status
61 silly pacote range manifest for micromatch@^3.1.8 fetched in 97ms
62 silly resolveWithNewModule micromatch@3.1.10 checking installable status
63 http fetch GET 200 hxxps://registry.npmjs.org/node-libs-browser 85ms
64 http fetch GET 200 hxxps://registry.npmjs.org/neo-async 98ms
65 silly pacote range manifest for node-libs-browser@^2.0.0 fetched in 96ms
66 silly resolveWithNewModule node-libs-browser@2.2.0 checking installable status
67 http fetch GET 200 https://registry.npmjs.org/schema-utils 84ms
68 silly pacote range manifest for neo-async@^2.5.0 fetched in 110ms
69 silly resolveWithNewModule neo-async@2.6.0 checking installable status
70 http fetch GET 200 hxxps://registry.npmjs.org/tapable 97ms
71 silly pacote range manifest for schema-utils@^1.0.0 fetched in 99ms
72 silly resolveWithNewModule schema-utils@1.0.0 checking installable status
73 http fetch GET 200 hxxps://registry.npmjs.org/terser-webpack-plugin 57ms
74 silly pacote range manifest for tapable@^1.1.0 fetched in 108ms
75 silly resolveWithNewModule tapable@1.1.1 checking installable status
76 http fetch GET 200 hxxps://registry.npmjs.org/mkdirp/-/mkdirp-0.5.1.tgz 57ms
77 silly pacote range manifest for mkdirp@~0.5.0 fetched in 145ms
78 silly resolveWithNewModule mkdirp@0.5.1 checking installable status
79 silly pacote range manifest for terser-webpack-plugin@^1.1.0 fetched in 69ms
80 silly resolveWithNewModule terser-webpack-plugin@1.2.2 checking installable status
81 http fetch GET 200 hxxps://registry.npmjs.org/watchpack 101ms
82 silly pacote range manifest for watchpack@^1.5.0 fetched in 110ms
83 silly resolveWithNewModule watchpack@1.6.0 checking installable status
84 http fetch GET 200 hxxps://registry.npmjs.org/@webassemblyjs%2fwasm-parser 502ms
85 silly pacote version manifest for @webassemblyjs/wasm-parser@1.8.2 fetched in 511ms
86 silly resolveWithNewModule @webassemblyjs/wasm-parser@1.8.2 checking installable status
87 http fetch GET 200 hxxps://registry.npmjs.org/webpack-sources 374ms
88 silly pacote range manifest for webpack-sources@^1.3.0 fetched in 382ms
89 silly resolveWithNewModule webpack-sources@1.3.0 checking installable status
90 http fetch GET 200 hxxps://registry.npmjs.org/@webassemblyjs%2fwast-parser 91ms
91 silly pacote version manifest for @webassemblyjs/wast-parser@1.8.2 fetched in 105ms
92 silly resolveWithNewModule @webassemblyjs/wast-parser@1.8.2 checking installable status
93 http fetch GET 200 hxxps://registry.npmjs.org/@webassemblyjs%2fhelper-wasm-bytecode 365ms
94 silly pacote version manifest for @webassemblyjs/helper-wasm-bytecode@1.8.2 fetched in 376ms
95 silly resolveWithNewModule @webassemblyjs/helper-wasm-bytecode@1.8.2 checking installable status
96 http fetch GET 200 hxxps://registry.npmjs.org/@webassemblyjs%2fhelper-api-error 93ms
97 silly pacote version manifest for @webassemblyjs/helper-api-error@1.8.2 fetched in 105ms
98 silly resolveWithNewModule @webassemblyjs/helper-api-error@1.8.2 checking installable status
99 http fetch GET 200 hxxps://registry.npmjs.org/@webassemblyjs%2ffloating-point-hex-parser 120ms
100 http fetch GET 200 hxxps://registry.npmjs.org/@webassemblyjs%2fhelper-fsm 121ms
101 silly pacote version manifest for @webassemblyjs/helper-fsm@1.8.2 fetched in 131ms
102 silly resolveWithNewModule @webassemblyjs/helper-fsm@1.8.2 checking installable status
103 silly pacote version manifest for @webassemblyjs/floating-point-hex-parser@1.8.2 fetched in 133ms
104 silly resolveWithNewModule @webassemblyjs/floating-point-hex-parser@1.8.2 checking installable status
105 http fetch GET 200 hxxps://registry.npmjs.org/@webassemblyjs%2fhelper-code-frame 304ms
106 silly pacote version manifest for @webassemblyjs/helper-code-frame@1.8.2 fetched in 318ms
107 silly resolveWithNewModule @webassemblyjs/helper-code-frame@1.8.2 checking installable status
108 silly fetchPackageMetaData error for long@git://github.com/dcodeIO/long.js.git#8181a6b50a2a230f0b2a1e4c4093f9b9d19c8b69 Error while executing:
108 silly fetchPackageMetaData C:\Program Files\Git\cmd\git.EXE ls-remote -h -t git://github.com/dcodeIO/long.js.git
108 silly fetchPackageMetaData
108 silly fetchPackageMetaData fatal: unable to connect to github.com:
108 silly fetchPackageMetaData github.com[0: 192.30.255.112]: errno=No such file or directory
108 silly fetchPackageMetaData github.com[1: 192.30.255.113]: errno=No such file or directory
108 silly fetchPackageMetaData
108 silly fetchPackageMetaData
108 silly fetchPackageMetaData exited with error code: 128
109 verbose stack RangeError: Maximum call stack size exceeded
109 verbose stack at RegExp.test ()
109 verbose stack at isDepOptional (C:\nodejs\node_modules\npm\lib\install\deps.js:405:45)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:414:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
109 verbose stack at failedDependency (C:\nodejs\node_modules\npm\lib\install\deps.js:430:9)
110 verbose cwd C:\Users\lus2
111 verbose Windows_NT 10.0.17134
112 verbose argv “C:\nodejs\node.exe” “C:\nodejs\node_modules\npm\bin\npm-cli.js” “install” “-g” “webpack”
113 verbose node v10.15.1
114 verbose npm v6.4.1
115 error Maximum call stack size exceeded
116 verbose exit [ 1, true ]

no matter what pack I try to install globally it always give me error of maximun call stack size exceeded and I try to run “npm cache clean --force”, but it no useful.

ps: As new user, I can not put more than 5 links so http change to hxxp


(John Gee) #2

Your log does have what might be a networking error unable to connect to github.com. Is the problem reproducible, or does the install work now? (Might be lucky!)

There are other people having similar issues in this thread, but no guaranteed work-arounds: Always Reproducible "Maximum call stack size exceeded" npm install error


(John Gee) #3

Explained in new comment in that thread, webpack issue: Always Reproducible "Maximum call stack size exceeded" npm install error


(system) closed #4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.