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.

Sign up for GitHub

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

Jump to bottom

cli no longer accepts arguments in Linux #307

Closed
ojeytonwilliams opened this issue Apr 8, 2020 · 2 comments
Closed

cli no longer accepts arguments in Linux #307

ojeytonwilliams opened this issue Apr 8, 2020 · 2 comments

Comments

@ojeytonwilliams
Copy link

Steps to reproduce:

npm install -g gscan@latest
gscan .

see

/usr/bin/env: ‘node --no-warnings’: No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines

it seems problem is that Linux only allows one argument to be passed after #! (discussed here), so it's ignoring everything after --no-warnings. Getting rid of that fixes it, anyway!
@daniellockyer
Copy link
Member

Thanks for the report @ojeytonwilliams! 😄

@ojeytonwilliams
Copy link
Author

You're welcome @daniellockyer and thanks, the new version works perfectly!

@ErisDS ErisDS mentioned this issue Apr 16, 2020
Closed
ErisDS added a commit that referenced this issue Apr 20, 2020
@ErisDS
OS-agnostic warning suppression
2f751df 
closes #309, refs #307, refs nodejs/node#32876

- removes all the weird flags from the shebang which explode various OSes
- instead use process.removeAllListeners() which should prevent warnings from being displayed using the node API and therefore in an OS-agnostic way
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@daniellockyer @ojeytonwilliams