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

Doesn't work on linux #2

Closed
truckingsim opened this issue Jan 12, 2017 · 4 comments
Closed

Doesn't work on linux #2

truckingsim opened this issue Jan 12, 2017 · 4 comments

Comments

@truckingsim
Copy link

The problem lies in the first line of index.js:

#!/usr/bin/env node --harmony

If you run this on linux you will get this error:

/usr/bin/env: ‘node --harmony’: No such file or directory

On linux (in both bash and zsh at least) you can't pass arguments and use /usr/bin/env. When using /usr/bin/env on linux, with arguments, it attempts to run 'node --harmony' as one program rather than node as the program with the --harmony argument.

This isn't a PR as I don't really have a solution for you as there isn't much of a work around this. I do question what do you need the --harmony argument for?

If it's not truly needed and you can work around it somehow then this would work fine on linux.

@truckingsim
Copy link
Author

Also forgot to add this only happens with shebang env (#!/usr/bin/env) you won't see this problem if you run /usr/bin/env node --harmony from the command line. That will work, but if you have a file and you use the shebang version you will run into this problem.

@prijindal
Copy link

Manually removing the harmony tag solves the problem

@truckingsim
Copy link
Author

@prijindal for sure, I just don't know why it was there to start with.

@junedomingo
Copy link
Owner

Hey guys, thanks for reporting. issue has been fixed. the --harmony tag is required by commander package because i'm not using babel back then and i didn't know that this can cause problem for other OS.

bomjkolyadun added a commit to bomjkolyadun/react-native-rename that referenced this issue Mar 24, 2022
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

3 participants