I am trying to create an ember application through command prompt
i installed Nodejs version v10.16.0 and then i use the command 'install npm install -g ember -cli' to install ember
ember successfully insatalled with version ember-cli 3.10.1 then i create a new application by using command 'ember new ember-quickstart' then i got the below error
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_logs\2019-07-02T09_36_58_880Z-debug.log Stack Trace and Error Report: C:\Users\KAGRAW~1.EME\AppData\Local\Temp/error.dump.4edeef2bba53a9733909115d695aa4ba.log
can someone help me to resolve the error.
Aucun commentaire:
Enregistrer un commentaire