- 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/
我通过 spring ioc 编写了一些 Rest 应用程序。但我无法解决这个问题。这是我的异常(exception): org.springframework.beans.factory.BeanC
我对 TestNG、Spring 框架等完全陌生,我正在尝试使用注释 @Value通过 @Configuration 访问配置文件注释。 我在这里想要实现的目标是让控制台从配置文件中写出“hi”,通过
为此工作了几个小时。我完全被难住了。 这是 CS113 的实验室。 如果用户在程序(二进制计算器)结束时选择继续,我们需要使用 goto 语句来到达程序的顶部。 但是,我们还需要释放所有分配的内存。
我正在尝试使用 ffmpeg 库构建一个小的 C 程序。但是我什至无法使用 avformat_open_input() 打开音频文件设置检查错误代码的函数后,我得到以下输出: Error code:
使用 Spring Initializer 创建一个简单的 Spring boot。我只在可用选项下选择 DevTools。 创建项目后,无需对其进行任何更改,即可正常运行程序。 现在,当我尝试在项目
所以我只是在 Mac OS X 中通过 brew 安装了 qt。但是它无法链接它。当我尝试运行 brew link qt 或 brew link --overwrite qt 我得到以下信息: ton
我在提交和 pull 时遇到了问题:在提交的 IDE 中,我看到: warning not all local changes may be shown due to an error: unable
我跑 man gcc | grep "-L" 我明白了 Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help' for more inf
我有一段代码,旨在接收任何 URL 并将其从网络上撕下来。到目前为止,它运行良好,直到有人给了它这个 URL: http://www.aspensurgical.com/static/images/a
在过去的 5 个小时里,我一直在尝试在我的服务器上设置 WireGuard,但在完成所有设置后,我无法 ping IP 或解析域。 下面是服务器配置 [Interface] Address = 10.
我正在尝试在 GitLab 中 fork 我的一个私有(private)项目,但是当我按下 fork 按钮时,我会收到以下信息: No available namespaces to fork the
我这里遇到了一些问题。我是 node.js 和 Rest API 的新手,但我正在尝试自学。我制作了 REST API,使用 MongoDB 与我的数据库进行通信,我使用 Postman 来测试我的路
下面的代码在控制台中给出以下消息: Uncaught DOMException: Failed to execute 'appendChild' on 'Node': The new child el
我正在尝试调用一个新端点来显示数据,我意识到在上一组有效的数据中,它在数据周围用一对额外的“[]”括号进行控制台,我认为这就是问题是,而新端点不会以我使用数据的方式产生它! 这是 NgFor 失败的原
我正在尝试将我的 Symfony2 应用程序部署到我的 Azure Web 应用程序,但遇到了一些麻烦。 推送到远程时,我在终端中收到以下消息 remote: Updating branch 'mas
Minikube已启动并正在运行,没有任何错误,但是我无法 curl IP。我在这里遵循:https://docs.traefik.io/user-guide/kubernetes/,似乎没有提到关闭
每当我尝试docker组成任何项目时,都会出现以下错误。 我尝试过有和没有sudo 我在这台机器上只有这个问题。我可以在Mac和Amazon WorkSpace上运行相同的容器。 (myslabs)
我正在尝试 pip install stanza 并收到此消息: ERROR: No matching distribution found for torch>=1.3.0 (from stanza
DNS 解析看起来不错,但我无法 ping 我的服务。可能是什么原因? 来自集群中的另一个 Pod: $ ping backend PING backend.default.svc.cluster.l
我正在使用Hibernate 4 + Spring MVC 4当我开始 Apache Tomcat Server 8我收到此错误: Error creating bean with name 'wel
我是一名优秀的程序员,十分优秀!