-
Notifications
You must be signed in to change notification settings - Fork 128
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
Documentation should mention dependency on the "node" binary #91
Comments
Thanks for reporting but I've never met this issue before. I think it depends on the way you install The alternative way to fix |
Yes, it was installed with |
Thanks @tkhduracell |
Same problem, |
|
helped me too |
Readme updated! |
Thanks for your post. I'm not sure how, but the nodejs-legacy package got uninstalled from my development machine and I was suddenly having problems with bower for no apparent reason. |
|
👍 nodejs-legacy |
Still true in August of 2015, apparently? This saved me on a search! |
Still true. |
+1 nodejs-legacy |
June/2016, still need to install nodejs-legacy to make it work |
Oh, I saw that it was mentioned in the Readme. Thanks again! |
The gem need the
node
-binary from nodejs-legacy in order to run.The error that appears when nodejs-legacy is not installed.
Solution:
Should the documentation mention this?
The text was updated successfully, but these errors were encountered: