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

/usr/bin/env: 'node': No such file or directory (ubuntu) #201

Closed
goldenbearkin opened this issue Sep 13, 2018 · 6 comments
Closed

/usr/bin/env: 'node': No such file or directory (ubuntu) #201

goldenbearkin opened this issue Sep 13, 2018 · 6 comments
Labels
type: bug Something isn't working type: feature New feature or request

Comments

@goldenbearkin
Copy link

when I try to new angular workspace, it shows below:

$ng new auth --collection=@schematics/angular
/usr/bin/env: 'node': No such file or directory

and I use nvm.

@goldenbearkin goldenbearkin changed the title /usr/bin/env: 'node': No such file or directory /usr/bin/env: 'node': No such file or directory (ubuntu) Sep 13, 2018
@vsavkin vsavkin added the type: bug Something isn't working label Sep 20, 2018
@patrickhousley
Copy link

patrickhousley commented Sep 21, 2018

I can confirm that if I start the app from the terminal, the node executable is found.

@alexeagle
Copy link

It would be nice for Angular Console to statically link the nodejs binary instead of relying on users to have already installed it.

@mrmeku
Copy link
Contributor

mrmeku commented Nov 29, 2018

We have no plans to add a statically linked version of nodejs as of right now. However, if anyone would want to add support for nvm via a PR that would be wonderful. I'm happy to provide any support that one would need to make the PR

@mrmeku mrmeku added the wontfix label Nov 29, 2018
@arjunyel
Copy link

For me at least Angular Console is working with nvm without launching it from the terminal, I have 11.8.0 aliased as the default

@NgxDev
Copy link

NgxDev commented Sep 5, 2021

Just switched to Windows/WSL2. And, while the commands work from the terminal (using zsh), if I try to do it from the VSCode extension, I get the "No such file or directory" error.
I'm not sure how NX works, and why doesn't it use the system's default terminal (zsh). It wants to use bash, and it seems to look at the .profile file, where NVM_DIR isn't set. NVM_DIR is set in ~/.bashrc and in ~/.zshrc
After I add the NVM stuff in the ~/.profile file, then the VSCode extension also works.
But if I think about it, since it's set in ~/.bashrc, isn't that where bash looks? This is strange...

@lesauf
Copy link

lesauf commented Nov 4, 2021

Just switched to Windows/WSL2. And, while the commands work from the terminal (using zsh), if I try to do it from the VSCode extension, I get the "No such file or directory" error. I'm not sure how NX works, and why doesn't it use the system's default terminal (zsh). It wants to use bash, and it seems to look at the .profile file, where NVM_DIR isn't set. NVM_DIR is set in ~/.bashrc and in ~/.zshrc After I add the NVM stuff in the ~/.profile file, then the VSCode extension also works. But if I think about it, since it's set in ~/.bashrc, isn't that where bash looks? This is strange...

Thanks. It works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working type: feature New feature or request
Projects
None yet
Development

No branches or pull requests

8 participants