Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm #19

Closed
wahabshah opened this issue Jun 9, 2015 · 9 comments
Closed

npm #19

wahabshah opened this issue Jun 9, 2015 · 9 comments

Comments

@wahabshah
Copy link

I tried installing yo using
npm install -g yo
but it gave the error for not having the correct version of npm installed
I already have the latest npm installed which is 2.11.1 as shown below:-
Kindly fix it, as i cannot installed generator like generator-ko


Your environment has been set up for using Node.js 0.12.4 (ia32) and npm.

C:\Users\kowsh>npm -version
2.11.1

C:\Users\kowsh>yo doctor

Yeoman Doctor
Running sanity checks on your system

V Global configuration file is valid
V NODE_PATH matches the npm root
V Node.js version
× npm version

Your npm version is outdated.

Upgrade to the latest version by running:
npm install -g npm

See this guide if you're having trouble upgrading:
https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

V No .bowerrc file in home directory
V No .yo-rc.json file in home directory

Found potential issues on your machine :(


@sindresorhus
Copy link
Member

It's just a warning. You can still use yo. Sounds like you have multiple versions of npm installed. I would recommend you to go through this guide: https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

@jcollum
Copy link

jcollum commented Nov 4, 2015

I'm using Node 4.20 LTS and getting this NPM error. But my version is the one that is bundled with the LTS:

$ npm --version
2.14.7

This doesn't seem like it should be an error. Using the npm version that comes with the LTS version of Node seems like a sensible thing to do that shouldn't be causing an error. This should be a warning at best.

@sindresorhus
Copy link
Member

npm@3 just didn't make the LTS release. npm@3 fixes so many issues that we would usually have to deal with. It's not an error. Just a very strong recommendation to upgrade. Pushing users to upgrade reduces the support burden for us, which means we can focus on actual features and issues instead of wasting time on endless npm install support triaging.

@jcollum
Copy link

jcollum commented Nov 4, 2015

When you put it in red text with a frowny face and a red x it sure looks like an error. You're sorta stuck with NPM 2.14.7 for a while; unfortunately I guess. I'm reluctant to use NPM 3 with Node 4 LTS specifically because it wasn't bundled. Who knows what sort of problems that could be creating...

@pelo8888
Copy link

npm update -g

@razahaider
Copy link

So I just fixed this by doing :

  1. /bin/bash -- login
  2. sudo apt-get remove --purge node
  3. sudo apt-get install nodejs
  4. sudo apt-get install npm
  5. npm update
  6. sudo npm install -g yo generator-kraken bower grunt-cli

Note : 1. was the most important step in my installation ;)

@sclanc sclanc mentioned this issue Mar 2, 2016
@mocheng
Copy link

mocheng commented Apr 20, 2016

I ran into same issue. Node version 4.4.2 and npm 2.15.0. I choose this version spec since it is LTS.

It would be appropriate to have yeoman run well with LTS version of node & npm.

@Rathishyedla
Copy link

You need to download latest version of node.js and npm Like(node.js v 6+ and npm v 3 +). Then it's works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants