Thought I’d quickly write this up as @kevinawalker and I had a mare with it yesterday on our windows boxes. I suspect it’s because I’d attempted to setup yeoman in the past before there was a nice npm install pathway, coupled with the lack of dependecies my machine (I installed an up to date ruby+python in between break and fix).
npm install –g yo
would appear to work and give solid feedback that everything appeared tickety boo. All PATH variables certainly indicated it would work, and ‘yo’ was discoverable in the path.
That said, typing anything other than yo –version would hang and never return (requiring a ctrl+c to break out of it).
When oldschool debugging through it (console.log for the win), turns out cli.js in the %APPDATA%/roaming/npm/node_modules/yo/cli.js was haning on line 76:
I didn’t follow down the pathway, though when npm installing yo on the mac it went through no bother.
npm uninstall –g yo
then a re-install didn’t help, whether or not we cleared the npm caches in between.
I still don’t know which magical combination of the above really worked (it may be that updating ruby/python between the old install and new was key, I can’t be sure) but the following steps fixed for both @kevinawalker and I:
- npm uninstall –g yo
- explorer window to %APPDATA%/roaming/npm-cache/
- delete ‘yo’ folder
- npm install –g yo
After that, all was well with the world.
Good luck, hope this helps someone!