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
Manually pointing PATH to yeoman after install #430
Comments
Afraid I'm not entirely sure what your issue is but I don't think it's specifically down to ZSH - I use ZSH and it worked fine for me. |
ZSH working fine for me too. Closing for now, since we can't reproduce. |
I should maybe mention that i am not the only user of this computer, but I do have administrator access. So maybe the issue is with multi-user installs? |
@chrisdl could you post up the results of the following?
Might shed some light. |
THIS OUTPUT IS FROM THE WRONG COMPUTER DISREGARD IT. Sure, check it out.
/Users/Christopher/.rvm/gems/ruby-1.8.7-head/bin:/Users/Christopher/.rvm/gems/ruby-1.8.7-head@global/bin:/Users/Christopher/.rvm/rubies/ruby-1.8.7-head/bin:/Users/Christopher/.rvm/bin::/usr/local/bin:/usr/bin:/bin:/usr/sbin:/usr/X11/bin:/usr/local/Cellar/coreutils/8.19/libexec/gnubin:/Users/Christopher/.rvm/bin
/usr/local/lib/node_modules |
@chrisdl Okay, this is me completely guessing... Maybe
To your |
edit: still wrong computer =( /edit I don't have npm in |
What version of Node are you running? I just upgraded from Node 0.8.1 to 0.8.8 and it comes with npm now (which it didn't used to do, at least not through brew installs), which is why my npm is in that directory. What does
Give? |
edit: still wrong comp /edit
|
In that case, I'd recommend adding Then perhaps try installing something else globally and see if it works, eg:
|
I just realized I've had a serious brain fart (in my defence I am running a fairly high fever). I'm not on the computer which has yeoman installed on it right now. I will return to this computer tonight and will test all your awesome suggestions and provide my |
Haha no worries :) I can't say with any confidence anything I've said might help, but might help narrow things down. Would be good to know if this is a Yeoman prob or your system set up. To be honest I suspect the later. |
Yeah I feel fairly certain something is simply not pointing to the right place. But I feel like my setup is fairly standard so I thought maybe yeoman install wasn't pointing something correctly, and that it was perhaps not just affecting me. |
Alright, back home now. I have now replaced When searching the computer for yeoman
The I removed yeoman using I thus conclude that the root cause of the issue seems to be that nothing in my paths are pointing at my npm modules. I re-added |
Awesome, glad you got it sorted. @sindresorhus is it maybe worth compiling some form of "troubleshooting" document or similar for common issues like this that I imagine might crop up a few times? I'll happily fork & try to put one together if you think it might be beneficial. |
Jack, can you add it to https://github.com/yeoman/yeoman/wiki/Additional-FAQ? Right now that's the easiest place to drop some documentation. Later on |
@paulirish just saw that you added a bit to the wiki, I'm happy to add a bit more detail to that additional FAQ so I'll do a bit of editing later. |
@jackfranklin Thanks :) |
Ran into this issue as well and decided to ask isaacs on #node.js. Seems like there are two similar but separate issues:
So the two workarounds are:
hth with the documentation. chat pasted below: 06:41:09 felideon | isaacs: any reason /usr/local/share/npm/bin would not be added to the path (mac 10.6.8) when installing the latest node binary (.pkg) from the website? |
Had the same problem installing node & npm using Homebrew. Solved by adding /usr/local/share/npm/bin to $PATH |
Ok. I've added the following two lines to my .bash_profile on Mac OS and that eliminated the path not found issue export PATH=/usr/local/share/npm/bin:$PATH But I'm getting a strange error when I actually try to create an app with Yeoman. Any help would be greatly appreciated!
UPDATE: As suggested I ran $ brew uninstall node and then reinstalled via the installer on nodejs.org and then upon installing Yeomin I ran into a permission error with simple $ npm install yo So trying with $ sudo npm install yo It seemed to work, but now to run $ yo webapp runs into the same permissione error as above, but upon running $ sudo yo webapp it created the project, but it installed EVERYTHING into the local /node_modules folder and everything is owned by root... #argh #wish-I-was-better-at-CL-things |
@brennannovak Yeoman don't have permission to that folder and throws. |
Ah yes, that did the trick, thanks @sindresorhus :) However running
Seems to install bower and about 20+ grunt modules into the local /node_modules folder instead of finding them in the gobal. Is this correct behavior? |
That's how node works and it's a good thing. http://blog.nodejs.org/2011/03/23/npm-1-0-global-vs-local-installation/ |
Hey ! I had the same trouble ! |
Ran into the same issue using ZSH and the yeoman plugin. The command below fixed it for me. |
Got the "There looks to be a problem with the install. :(" message and tried uninstalling, reinstalling cleaning npm cache etc.
Also tried installing with
curl -L get.yeoman.io | bash
andcurl -L get.yeoman.io | sh
and doing a manual install.I think the issue might be that I use ZSH? I solved the issue by manually adding
/usr/local/share/npm/lib/node_modules/yeoman/bin/
in my ~/.zshrc file.Yeoman now seems to be working correctly.
Did I miss something obvious? Was there some other fix? What was causing the issue?
The text was updated successfully, but these errors were encountered: