通过 cmd 创建 ember 应用程序时出现以下错误

I am getting the following error while creating the ember application through cmd

我正在尝试通过命令提示符创建一个 ember 应用程序

我安装了 Nodejs 版本 v10.16.0 然后我使用命令 npm install -g ember -cli 安装 ember。 ember 成功安装版本 ember-cli 3.10.1.

然后我使用命令 ember new ember-quickstart 创建了一个新应用程序。然后我得到以下错误:

Error creating new application. Removing generated directory `./kushi`
Command failed: npm install --loglevel error
npm WARN deprecated @babel/polyfill@7.4.4:  As of Babel 7.4.0, this
npm WARN deprecated package has been deprecated in favor of directly
npm WARN deprecated including core-js/stable (to polyfill ECMAScript
npm WARN deprecated features) and regenerator-runtime/runtime
npm WARN deprecated (needed to use transpiled generator functions):
npm WARN deprecated
npm WARN deprecated import "core-js/stable";
npm WARN deprecated import "regenerator-runtime/runtime";
npm WARN deprecated exists-sync@0.0.4: Please replace with usage of fs.existsSync
npm WARN tar ENOENT: no such file or directory, open 
'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\broccoli-rollup-93db1951\dist\index.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\broccoli-rollup-93db1951\dist\index.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-typescript-b54d1b7c\js\blueprints\ember-cli-typescript\index.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-typescript-b54d1b7c\js\lib\commands\clean.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-typescript-b54d1b7c\js\lib\commands\precompile.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-typescript-b54d1b7c\js\lib\utilities\copy-declarations.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-typescript-b54d1b7c\js\lib\utilities\ember-cli-entities.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-typescript-b54d1b7c\js\lib\utilities\fork.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-typescript-b54d1b7c\blueprint-files\ember-cli-typescript\__config_root__\config\environment.d.ts'
npm WARN tar ENOENT: no 
such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-typescript-b54d1b7c\blueprint-files\ember-cli-typescript\types\__app_name__\index.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-5cfc18ea\blueprints\module-unification-app\files\src\ui\routes\application\template.hbs'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-5cfc18ea\lib\tasks\server\middleware\broccoli-watcher\index.js'
npm WARN tar ENOENT: no such file or directory, open 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-5cfc18ea\lib\tasks\server\middleware\broccoli-watcher\package.json'
npm WARN tar ENOENT: no such file or directory, lstat 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-5cfc18ea\lib\tasks\server\middleware'
npm WARN tar ENOENT: no such file or directory, lstat 'C:\Users\kagrawal.EMEAAD\Desktop\kushi\node_modules\.staging\ember-cli-5cfc18ea\lib'
npm ERR! code ERR_INVALID_OPT_VALUE
npm ERR! The value "false" is invalid for option "readableHighWaterMark"
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\kagrawal.EMEAAD\AppData\Roaming\npm-cache\_logs19-07-02T09_36_58_880Z-debug.log
Stack Trace and Error Report: C:\Users\KAGRAW~1.EME\AppData\Local\Temp/error.dump.4edeef2bba53a9733909115d695aa4ba.log

有人可以帮我解决这个错误吗?

奥拉@dhS,

我注意到您在回答中说 Ember 不支持节点 10,这不是真的。 Ember 的节点支持通常取决于它的测试内容和当前的持续集成 (CI) 运行 节点 8、10、11 和 12。

您的 npm 安装可能存在权限问题或潜在问题,如果没有该错误末尾列出的文件内容,则很难诊断这些问题:

Stack Trace and Error Report: C:\Users\KAGRAW~1.EME\AppData\Local\Temp/error.dump.4edeef2bba53a9733909115d695aa4ba.log

下次您遇到这样的错误时,拥有此文件的内容会非常有帮助

此外,您发布的大部分错误都是警告,可能与您计算机上的权限问题有关如果您再次遇到此问题,可能值得升级 您的 Node 版本或重新安装它,并通过 运行ning 确保您使用的是最新的 npm 版本:

npm i -g npm@latest

这个问题的专业修复

通过 运行 检查你的 npm 版本:npm -v

找到您 运行 的版本后,通过检查 package.json 确认此版本,并检查引擎...您将看到项目所需的 npm 和节点版本。

将您的 npm 版本升级到 package.json

上反映的版本