我正在尝试通过命令提示
创建一个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:Userskagrawal.EMEAADDesktopkushinode_modules.stagingbroccoli-rollup-93db1951distindex.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingbroccoli-rollup-93db1951distindex.js'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-typescript-b54d1b7cjsblueprintsember-cli-typescriptindex.js'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-typescript-b54d1b7cjslibcommandsclean.js'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-typescript-b54d1b7cjslibcommandsprecompile.js'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-typescript-b54d1b7cjslibutilitiescopy-declarations.js'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-typescript-b54d1b7cjslibutilitiesember-cli-entities.js'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-typescript-b54d1b7cjslibutilitiesfork.js'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-typescript-b54d1b7cblueprint-filesember-cli-typescript__config_root__configenvironment.d.ts'
npm WARN tar ENOENT: no
such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-typescript-b54d1b7cblueprint-filesember-cli-typescripttypes__app_name__index.d.ts'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-5cfc18eablueprintsmodule-unification-appfilessrcuiroutesapplicationtemplate.hbs'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-5cfc18ealibtasksservermiddlewarebroccoli-watcherindex.js'
npm WARN tar ENOENT: no such file or directory, open 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-5cfc18ealibtasksservermiddlewarebroccoli-watcherpackage.json'
npm WARN tar ENOENT: no such file or directory, lstat 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-5cfc18ealibtasksservermiddleware'
npm WARN tar ENOENT: no such file or directory, lstat 'C:Userskagrawal.EMEAADDesktopkushinode_modules.stagingember-cli-5cfc18ealib'
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:Userskagrawal.EMEAADAppDataRoamingnpm-cache_logs2019-07-02T09_36_58_880Z-debug.log
Stack Trace and Error Report: C:UsersKAGRAW~1.EMEAppDataLocalTemp/error.dump.4edeef2bba53a9733909115d695aa4ba.log
有人可以帮助我解决错误吗？
ola @dhs，
我在您的回答中注意到您说Ember不支持Node 10，这是不正确的。对Ember的节点支持通常取决于它的测试，并且电流连续集成(CI(正在使用节点8、10、11和12进行。
>您可能存在权限问题或NPM安装的某些问题，而没有该错误末尾列出的文件内容，很难诊断出很难诊断：
Stack Trace and Error Report: C:UsersKAGRAW~1.EMEAppDataLocalTemp/error.dump.4edeef2bba53a9733909115d695aa4ba.log
下次有这样的错误时，拥有此文件的内容🎉
将非常有帮助另外，您发布的大多数错误都是警告，可能与计算机上的权限问题有关，如果您再次遇到此问题，则可能值得升级您的节点版本或重新安装它，并确保通过运行：
来确保您处于最新的NPM版本。npm i -g npm@latest
这个问题的专业解决方案
通过运行：NPM -V
检查您的NPM版本找到运行的版本后，通过检查软件包来确认此版本，然后检查引擎...您将看到项目所需的NPM和节点版本。
将您的NPM版本升级到包装上反映的版本。JSON