npm - Githubissues

yeoman / doctor

Detect potential issues with users system that could prevent Yeoman from working correctly

http://yeoman.io

BSD 2-Clause "Simplified" License

61 stars 17 forks source link

npm #19

Closed wahabshah closed 9 years ago

wahabshah commented 9 years ago

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 commented 9 years ago

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 commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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...