Closed jgornick closed 10 years ago
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.
I'm suffering from the same issue and I don't have any idea how this is happening or how to solve this.
Have you tried an older version of bower? Maybe this could sovle your problem
@Spea Yes, I just tried some of the latest commits and the issue occurred since the compatibility to Bower 1.0.0.
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 :)
https://github.com/joyent/node/issues/3911
This is how i solved it
sudo ln -s /usr/bin/nodejs /usr/bin/node
glad to hear you were able to fix this issue :)
I added the SpBowerBundle to my application and after I clear the cache and I load a controller action, I get the following exception:
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:
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?