- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
D:\Programming\React\Project1>npm install --save-dev webpack
npm ERR! Maximum call stack size exceeded
这是我在尝试安装 webpack 时遇到的错误。我有节点版本 10.50 现在我有节点 11.10.0 和 npm 6.7.0
我做了 cache clean --force ,但没有帮助。我安装了 react, react-dom babel 但 webpack 给出了这个错误。我尝试使用 --save-dev 安装它,没有它,结果是一样的。日志文件是
0 info it worked if it ends with ok
1 verbose cli [ 'D:\\Program Files\\Node\\node.exe',
1 verbose cli 'D:\\Program Files\\Node\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'install',
1 verbose cli '--save-dev',
1 verbose cli 'webpack' ]
2 info using npm@6.7.0
3 info using node@v11.10.0
4 verbose npm-session 85b41b11615ec8a8
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 200 https://registry.npmjs.org/webpack 377ms
8 silly pacote tag manifest for webpack@latest fetched in 413ms
9 timing stage:loadCurrentTree Completed in 804ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 3ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 179ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule webpack@4.29.4 checking installable status
17 http fetch GET 200 https://registry.npmjs.org/@webassemblyjs%2fast 80ms
18 silly pacote version manifest for @webassemblyjs/ast@1.8.2 fetched in 88ms
19 silly resolveWithNewModule @webassemblyjs/ast@1.8.2 checking installable status
20 http fetch GET 200 https://registry.npmjs.org/ajv-keywords 148ms
21 http fetch GET 200 https://registry.npmjs.org/chrome-trace-event 149ms
22 http fetch GET 200 https://registry.npmjs.org/acorn-dynamic-import 158ms
23 http fetch GET 200 https://registry.npmjs.org/acorn 165ms
24 http fetch GET 200 https://registry.npmjs.org/enhanced-resolve 162ms
25 http fetch GET 200 https://registry.npmjs.org/eslint-scope 98ms
26 silly pacote range manifest for chrome-trace-event@^1.0.0 fetched in 177ms
27 silly resolveWithNewModule chrome-trace-event@1.0.0 checking installable status
28 silly pacote range manifest for ajv-keywords@^3.1.0 fetched in 184ms
29 silly resolveWithNewModule ajv-keywords@3.4.0 checking installable status
30 silly pacote range manifest for enhanced-resolve@^4.1.0 fetched in 193ms
31 silly resolveWithNewModule enhanced-resolve@4.1.0 checking installable status
32 silly pacote range manifest for acorn-dynamic-import@^4.0.0 fetched in 206ms
33 silly resolveWithNewModule acorn-dynamic-import@4.0.0 checking installable status
34 silly pacote range manifest for acorn@^6.0.5 fetched in 209ms
35 silly resolveWithNewModule acorn@6.1.0 checking installable status
36 silly pacote range manifest for eslint-scope@^4.0.0 fetched in 135ms
37 silly resolveWithNewModule eslint-scope@4.0.0 checking installable status
38 http fetch GET 200 https://registry.npmjs.org/@webassemblyjs%2fwasm-edit 236ms
39 http fetch GET 200 https://registry.npmjs.org/ajv 229ms
40 http fetch GET 200 https://registry.npmjs.org/@webassemblyjs%2fhelper-module-context 245ms
41 http fetch GET 200 https://registry.npmjs.org/json-parse-better-errors 57ms
42 http fetch GET 200 https://registry.npmjs.org/@webassemblyjs%2fwasm-parser 249ms
43 http fetch GET 200 https://registry.npmjs.org/loader-runner 68ms
44 silly pacote version manifest for @webassemblyjs/wasm-edit@1.8.2 fetched in 279ms
45 silly resolveWithNewModule @webassemblyjs/wasm-edit@1.8.2 checking installable status
46 silly pacote range manifest for ajv@^6.1.0 fetched in 273ms
47 silly resolveWithNewModule ajv@6.9.1 checking installable status
48 http fetch GET 200 https://registry.npmjs.org/memory-fs 74ms
49 http fetch GET 200 https://registry.npmjs.org/micromatch 71ms
50 silly pacote version manifest for @webassemblyjs/helper-module-context@1.8.2 fetched in 289ms
51 silly resolveWithNewModule @webassemblyjs/helper-module-context@1.8.2 checking installable status
52 silly pacote version manifest for @webassemblyjs/wasm-parser@1.8.2 fetched in 290ms
53 silly resolveWithNewModule @webassemblyjs/wasm-parser@1.8.2 checking installable status
54 silly pacote range manifest for json-parse-better-errors@^1.0.2 fetched in 106ms
55 silly resolveWithNewModule json-parse-better-errors@1.0.2 checking installable status
56 silly pacote range manifest for loader-runner@^2.3.0 fetched in 102ms
57 silly resolveWithNewModule loader-runner@2.4.0 checking installable status
58 http fetch GET 200 https://registry.npmjs.org/node-libs-browser 78ms
59 http fetch GET 200 https://registry.npmjs.org/neo-async 91ms
60 silly pacote range manifest for micromatch@^3.1.8 fetched in 96ms
61 silly resolveWithNewModule micromatch@3.1.10 checking installable status
62 silly pacote range manifest for memory-fs@~0.4.1 fetched in 100ms
63 silly resolveWithNewModule memory-fs@0.4.1 checking installable status
64 silly pacote range manifest for node-libs-browser@^2.0.0 fetched in 90ms
65 silly resolveWithNewModule node-libs-browser@2.2.0 checking installable status
66 silly pacote range manifest for neo-async@^2.5.0 fetched in 101ms
67 silly resolveWithNewModule neo-async@2.6.0 checking installable status
68 http fetch GET 200 https://registry.npmjs.org/tapable 43ms
69 http fetch GET 200 https://registry.npmjs.org/terser-webpack-plugin 52ms
70 http fetch GET 200 https://registry.npmjs.org/webpack-sources 44ms
71 http fetch GET 200 https://registry.npmjs.org/schema-utils 63ms
72 silly pacote range manifest for tapable@^1.1.0 fetched in 64ms
73 silly resolveWithNewModule tapable@1.1.1 checking installable status
74 http fetch GET 200 https://registry.npmjs.org/watchpack 56ms
75 silly pacote range manifest for terser-webpack-plugin@^1.1.0 fetched in 65ms
76 silly resolveWithNewModule terser-webpack-plugin@1.2.2 checking installable status
77 silly pacote range manifest for webpack-sources@^1.3.0 fetched in 57ms
78 silly resolveWithNewModule webpack-sources@1.3.0 checking installable status
79 silly pacote range manifest for schema-utils@^1.0.0 fetched in 75ms
80 silly resolveWithNewModule schema-utils@1.0.0 checking installable status
81 silly pacote range manifest for watchpack@^1.5.0 fetched in 64ms
82 silly resolveWithNewModule watchpack@1.6.0 checking installable status
83 http fetch GET 200 https://registry.npmjs.org/@webassemblyjs%2fwast-parser 48ms
84 silly pacote version manifest for @webassemblyjs/wast-parser@1.8.2 fetched in 57ms
85 silly resolveWithNewModule @webassemblyjs/wast-parser@1.8.2 checking installable status
86 http fetch GET 200 https://registry.npmjs.org/@webassemblyjs%2fhelper-wasm-bytecode 71ms
87 silly pacote version manifest for @webassemblyjs/helper-wasm-bytecode@1.8.2 fetched in 77ms
88 silly resolveWithNewModule @webassemblyjs/helper-wasm-bytecode@1.8.2 checking installable status
89 silly fetchPackageMetaData error for long@git://github.com/dcodeIO/long.js.git#8181a6b50a2a230f0b2a1e4c4093f9b9d19c8b69 Error while executing:
89 silly fetchPackageMetaData undefined ls-remote -h -t git://github.com/dcodeIO/long.js.git
89 silly fetchPackageMetaData
89 silly fetchPackageMetaData
89 silly fetchPackageMetaData spawn git ENOENT
90 verbose stack RangeError: Maximum call stack size exceeded
90 verbose stack at RegExp.test (<anonymous>)
90 verbose stack at isDepOptional (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:405:45)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:414:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
90 verbose stack at failedDependency (D:\Program Files\Node\node_modules\npm\lib\install\deps.js:430:9)
91 verbose cwd D:\Programming\React\Project1
92 verbose Windows_NT 6.1.7601
93 verbose argv "D:\\Program Files\\Node\\node.exe" "D:\\Program Files\\Node\\node_modules\\npm\\bin\\npm-cli.js" "install" "--save-dev" "webpack"
94 verbose node v11.10.0
95 verbose npm v6.7.0
96 error Maximum call stack size exceeded
97 verbose exit [ 1, true ]
我该如何解决,请各位指点。
最佳答案
安装以前的版本对我有用:
npm install webpack@4.29.3 --save-dev
关于npm无法安装webpack,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/54730865/
我听说最好不要从您系统的 Perl 版本所在的 CPAN 安装模块。我知道如何使用命令行安装模块,我只是想知道是否有办法将 CPAN 与系统核心 Perl 分开。 我应该: 下载源代码并专门为这些模块
我听说最好不要从系统的 Perl 版本所在的 CPAN 安装模块。我知道如何使用命令行安装模块,我只是想知道是否有办法将 CPAN 与系统的核心 Perl 分开。 我应该: 下载源代码并专门为这些模块
单独安装 electron 与通过 electron-builder 安装有什么区别?我正在使用 React 构建一个 Electron 应用程序,并且已经找到了一些教程。它们安装 Electron
两者安装有什么区别?我按照安装页面上的说明在全局范围内安装了 webpack,然后我转到了入门指南,据说在那里可以在本地安装 webpack-cli。 CLI = Command Line Inter
我在 OS X Yosemite 上用 PHP 安装了默认的 Apache 服务器,安装了 pear,用 brew 安装了 Solr (brew install solr),现在我正在尝试使用 PEC
我解压并编译了 Ruby 2.1 并安装了几个支持工具。 但是当我安装了 libssl-dev 时,OpenSSL 不会安装。 我在支持 openssl 时遇到这个错误: make: *** No r
我在 android studio 2.3.1 和 gradle 3.2 中设计了 2 到 3 个应用程序。当我从它运行应用程序到任何设备或模拟器时,一切都工作正常。但是当我从构建文件夹中获取该 ap
我注意到我正在读一本书提到通过 apt-get 安装 numpy 和 opencv apt-get install python-numpy python-opencv 但我可以通过以下方式在 pip
我正在尝试在 Windows 8.1 上安装 ansicon。我提取了文件并达到了我需要调用 ansicon -i 的级别。当我在 cmd 中输入此内容并运行 python 脚本时效果很好,但是当我通
我有 linux MINT 17.3 Kernel 4.4.0-81 所有更新可用。 (由于不同的原因,我无法迁移到更新版本的 ubuntu/mint) 我已经通过 PPA 安装了 FFMPEG(不是
尝试在本地运行我的应用程序时出现错误: 我只在 chrome 浏览器中收到此错误。我尝试过不同的东西,但我不确定为什么它是 Chrome 特定的。 最佳答案 我怀疑这不是 Firebase 问题,而是
这是我第一次开发 AngularJS 应用程序并使用脚手架工具 Yeoman ( http://yeoman.io/ )。我想对我的一些图标使用 fontawesome ( http://fortaw
我知道您通常“应该”$ pip install 如果包没有 brew ,但如果有一个你想安装的 python 包,你可以使用 $ pip install或 $ brew install为了?例如,通过
我正在尝试通过 RVM 安装 Ruby 1.9.3。然而,当谈到安装 RubyGems 时,我得到了这个: curl: (22) The requested URL returned error: 4
我是真正提出问题的新手,但你去吧。 我一直在尝试按照安装指南添加 dnsname: https://github.com/containers/dnsname https://github.com/c
Studio更新至0.4.0 建筑产量为“需要1.8版Gradle”;将设置设置为1.8 bin目录; 建立 “要求1.9级”;将设置设置为1.9 bin; 建立 “要求1.8级” 啊。不知道该怎么做
我刚刚注意到 kernel.org 因维护而停机。是否有使用不同镜子的不同公式?或者我可以向 Homebrew 软件添加不同的来源(如 bundler ?)? 谢谢你的帮助! 最佳答案 快速解决方法:
当我运行时: peardev install phpunit/PHPUnit 我得到以下信息: No releases available for package "pear.phpunit.de/P
服务器操作系统为Fedora 24. 64bit。 我想安装 Git 2.6.6。 所以下载源码并安装。 此服务器离线。所以我不使用“yum”。 ./configure --prefix=/usr/l
我正在尝试在我自己的服务器(操作系统:Linux Ubuntu Server 12.04)上安装 OpenEdX,但我遇到了同样的错误。谁能帮帮我? TASK: [ insights | insta
我是一名优秀的程序员,十分优秀!