11

I am trying to install yo on my ubuntu v16.4 LTS but i get this error:

npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
npm ERR! Linux 4.4.0-22-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "yo"
npm ERR! node v6.2.0
npm ERR! npm  v3.9.0
npm ERR! path /usr/local/lib/node_modules/yo/lib/cli.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/yo/lib/cli.js'
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/yo/lib/cli.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! Please include the following file with any support request:
npm ERR!     /home/momor1/npm-debug.log

As you see, I have the latest npm and nodejs, and I am in root mode so I still don't get it why its throwing this error. Any help please:)

Vini.g.fer
  • 11,639
  • 16
  • 61
  • 90
Kob_24
  • 592
  • 1
  • 10
  • 26

2 Answers2

13

It seems that this error occurs when you are trying to install the latest version, which was released today (2016/04/18): 1.8.2

Please try to install the previous version:

sudo npm install -g yo@1.8.1

This is working for me now. Tested on a clean virtual machine with OS X El Capitan v10.11.2, node 4.4.4 and npm 3.9.0 and on my developer machine with OS X 10.11.5.

Christian Junk
  • 1,000
  • 1
  • 8
  • 22
  • This worked for me. @Kob_24 try `npm cache clean` first? I was able to confirm on my build server that the problem started once the yo package was upgraded from 1.8.1 to 1.8.2 – OnResolve May 18 '16 at 13:48
  • i still get the same even if i do npm cache clean, how did you upgrade from 18.1 to 1.8.2? – Kob_24 May 18 '16 at 13:50
  • YSK it's considered a Bad Idea to install npm modules with sudo; here are instructions for working around it http://www.competa.com/blog/2014/12/how-to-run-npm-without-sudo/ – jcollum May 18 '16 at 16:34
0

Thanks to @jcollum to help me find the solution, the problem was that yo needed to install some plugins in sudo mode (this was not possible since installation was automatic by yo). Setting the prefix of npm to home would solve the issue of using sudo each time u need to install new package. Just follow this tutorial and you should be able to install yo@1.8.3. Best of Luck http://www.competa.com/blog/2014/12/how-to-run-npm-without-sudo/

Kob_24
  • 592
  • 1
  • 10
  • 26