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

OSX 10.8.5 node no such file or directory on bower list --json #44

Closed
jgornick opened this issue Sep 14, 2013 · 7 comments
Closed

OSX 10.8.5 node no such file or directory on bower list --json #44

jgornick opened this issue Sep 14, 2013 · 7 comments

Comments

@jgornick
Copy link

I added the SpBowerBundle to my application and after I clear the cache and I load a controller action, I get the following exception:

Sp\BowerBundle\Bower\Exception\CommandException: Something went wrong while executing the command '/usr/local/share/npm/bin/bower' 'list' '--json' '-V' env: node: No such file or directory...

The exception isn't thrown for any requests after. I'm assuming it has something to do with a cache warmup?

I have check my path for my user and globally and the path to node and bower and they exist:

/usr/local/opt/php53/bin:/usr/local/bin:/usr/local/sbin:/usr/local/share/python:/usr/local/share/npm/bin:/usr/local/opt/ruby/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/local/sbin:/usr/local/share/python:/usr/local/share/npm/bin:/usr/local/opt/ruby/bin

You'll notice that some of it is duplicated because I'm using paths.d solution to add the path to any npm bins and homebrew bins (usr/local/bin) to my global path.

Thoughts?

@Spea
Copy link
Owner

Spea commented Sep 22, 2013

Hey there, sadly I can not reproduce this issue on my system (I also don't have a mac around here). I think it has something to do with your node setup, but no sure.

@daFish
Copy link
Contributor

daFish commented Sep 29, 2013

I'm suffering from the same issue and I don't have any idea how this is happening or how to solve this.

@Spea
Copy link
Owner

Spea commented Sep 29, 2013

Have you tried an older version of bower? Maybe this could sovle your problem

@daFish
Copy link
Contributor

daFish commented Sep 29, 2013

@Spea Yes, I just tried some of the latest commits and the issue occurred since the compatibility to Bower 1.0.0.

@Spea
Copy link
Owner

Spea commented Oct 3, 2013

I try to reproduce this on my linux machine, but I can not guarantee it. If you have any suggestions on how to fix this, a PR would be highly appreciated :)

@kaiwa
Copy link
Contributor

kaiwa commented Oct 20, 2013

nodejs/node-v0.x-archive#3911

This is how i solved it

sudo ln -s /usr/bin/nodejs /usr/bin/node

@Spea
Copy link
Owner

Spea commented Oct 20, 2013

glad to hear you were able to fix this issue :)

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

4 participants