Ionic error to start app

Asked

Viewed 559 times

1

I’m starting my studies with Ionic v2. I upgraded the Ionic version to v2 however when I run the command ionic start wiltonfinances blank --v2 and displayed an error message.

See the information displayed on the console :

MINGW64

wilton@WILTONPROCOPIO MINGW64  /c/projetocordova (master) 
$ ionic start wiltonfinances blank --v2 

One awesome Ionic app coming right up... 

Creating Ionic app in folder C:\projetocordova\wiltonfinances based on blank project 

Downloading: https://github.com/driftycolionic2-app-base/archive/master.zip 

Downloading: https://github.com/driftyco/ionic2-starter-blank/archive/master.zip 

Installing npm packages... 

Unable to run spawn commandError: spawn npm ENOENT (CLI v2.0.0-beta.23) 

Your system information:

Cordova CLI: 4.2.0 
Gulp version: CLI version 3.9.0 
Gulp local: 
Ionic CLI Version: 2.0.0-beta.23 
Ionic App Lib Version: 2.0.0-beta.13
OS: 
Node Version: v4.4.1 

Error

Unable to run Spawn commandError: Spawn npm ENOENT (CLI v2.0.0-beta.23)

You can also view error message by clicking here.

  • Welcome to the OS. Try to supplement your questions in order to facilitate the understanding of others. For example, the previous version worked?

  • You have Ode.js installed?

  • Welcome, Wilton. Avoid using images to describe errors. It is preferable to paste the error in the question to facilitate the search for people who will have the same mistake in the future. If using an image, do not omit the image description.

  • Wilton there are online solutions where you can convert "text image" that can improve the statement of the questions, I like and used to edit your topic the solution provided on this site http://www.onlineocr.net/

  • Do you have any reason to use these "old versions"?

1 answer

0

Good morning,

at this link ENOENT error when Doing Ionic start

apparently the same error occurs, according to the answer accepted by the author, the solution was this:

"I have exactly the same problem. It worked in beta 22.

Reverting to the previous beta solved the problem:

install npm -g [email protected] "

I hope I’ve helped!

Browser other questions tagged

You are not signed in. Login or sign up in order to post.