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

Documentation should mention dependency on the "node" binary #91

Closed
tkhduracell opened this issue Jul 10, 2014 · 15 comments
Closed

Documentation should mention dependency on the "node" binary #91

tkhduracell opened this issue Jul 10, 2014 · 15 comments

Comments

@tkhduracell
Copy link

The gem need the node-binary from nodejs-legacy in order to run.

The error that appears when nodejs-legacy is not installed.

/vagrant vagrant@vagrant-ubuntu-trusty-64% rake bower:list
/usr/local/bin/bower list
rake aborted!
Command failed with status (1): [/usr/local/bin/bower list...]

Tasks: TOP => bower:list
(See full trace by running task with --trace)
/vagrant vagrant@vagrant-ubuntu-trusty-64% rake bower:install
bower.js files generated
/usr/local/bin/bower install
/usr/bin/env: node: No such file or directory
rake aborted!
Command failed with status (127): [/usr/local/bin/bower install ...]

Tasks: TOP => bower:install
(See full trace by running task with --trace)

Solution:

 sudo apt-get install nodejs-legacy

Should the documentation mention this?

@SergeyKishenin
Copy link
Collaborator

Thanks for reporting but I've never met this issue before. I think it depends on the way you install node (you did it via package manager, right?) and it not related to bower-rails.

The alternative way to fix /usr/bin/env: node: No such file or directory error is to create a symlink like ln -s /usr/bin/nodejs /usr/bin/node nodejs/node-v0.x-archive#3911 (comment)

@tkhduracell
Copy link
Author

Yes, it was installed with apt-get. Ok, thanks for your help

@RajRoR
Copy link

RajRoR commented Oct 9, 2014

Thanks @tkhduracell sudo apt-get install nodejs-legacy saved me. 👍

@nynj
Copy link

nynj commented Oct 18, 2014

Same problem, sudo apt-get install nodejs-legacy worked for me as well. Ubuntu 13.10.

@mohitsethi
Copy link

nodejs-legacy works on Ubuntu 14.04 as well

@bernstein7
Copy link

helped me too

SergeyKishenin added a commit that referenced this issue Dec 12, 2014
@SergeyKishenin
Copy link
Collaborator

Readme updated!

@FooBarRaz
Copy link

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.

@gil27
Copy link

gil27 commented Apr 20, 2015

nodejs-legacy ❤️

@ajahongir
Copy link

👍 nodejs-legacy

@astrostl
Copy link

astrostl commented Aug 7, 2015

Still true in August of 2015, apparently? This saved me on a search!

@gdurelle
Copy link

Still true.
💚 nodejs-legacy ❤️

@0rtep
Copy link

0rtep commented Dec 9, 2015

+1 nodejs-legacy

@MingStar
Copy link

June/2016, still need to install nodejs-legacy to make it work
+1 Thanks!

@MingStar
Copy link

Oh, I saw that it was mentioned in the Readme. Thanks again!

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