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

nvm run unstable --harmony returns 'bad option' #641

Closed
ghost opened this issue Jan 31, 2015 · 2 comments
Closed

nvm run unstable --harmony returns 'bad option' #641

ghost opened this issue Jan 31, 2015 · 2 comments
Assignees
Labels
bugs Oh no, something's broken :-(

Comments

@ghost
Copy link

ghost commented Jan 31, 2015

$ nvm run unstable --harmony index.js

And result:

Running node v0.11.16
node: bad option: --harmony index.js

Is it not supposed to work?


$ nvm use unstable
$ node --harmony index.js

works fine.

@ljharb
Copy link
Member

ljharb commented Feb 1, 2015

Hmm - I think the way nvm run is calling node isn't working as you'd expect.

I consider this a bug. Thanks for reporting!

@ljharb ljharb self-assigned this Feb 1, 2015
@ljharb ljharb added the bugs Oh no, something's broken :-( label Feb 1, 2015
@ljharb
Copy link
Member

ljharb commented Feb 3, 2015

I've got a fix ready for this but one of the tests refuses to pass in one shell; I'll keep working on it.

@ljharb ljharb closed this as completed in be56ff3 Feb 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugs Oh no, something's broken :-(
Projects
None yet
Development

No branches or pull requests

1 participant