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

Rename node -> iojs #249

Closed
piscisaureus opened this issue Jan 7, 2015 · 8 comments
Closed

Rename node -> iojs #249

piscisaureus opened this issue Jan 7, 2015 · 8 comments
Assignees
Milestone

Comments

@piscisaureus
Copy link
Contributor

No description provided.

@piscisaureus piscisaureus added this to the v1.0.0 milestone Jan 7, 2015
@piscisaureus
Copy link
Contributor Author

@bnoordhuis Please let me know when you have a PR - I'll put in my node.exe stub.

@ruimarinho
Copy link

@isaacs is there any adjustment on npm that needs to be made in order to keep it compatible with this rename or will a symlink to node be created precisely to avoid that?

@isaacs
Copy link
Contributor

isaacs commented Jan 8, 2015

npm uses the binary name node. Roughly 100% of all existing bin scripts do the same. The symlink is absolutely necessary.

@ruimarinho
Copy link

Will there be any way of npm using some kind of feature detection to decide whether to use feature A or B when running under io.js? For instance, leveraging an important performance optimization.

@isaacs
Copy link
Contributor

isaacs commented Jan 8, 2015

@ruimarinho Just the standard stuff you already have. process.execPath, process.version, feature detection for the existence of specific functions/etc.

@rvagg
Copy link
Member

rvagg commented Jan 8, 2015

on Windows we will likely end up with process.execPath being node.exe without the luxury of following a symlink to iojs so that's going to be tricky

@piscisaureus
Copy link
Contributor Author

I'll take care of the alias.

@cjihrig
Copy link
Contributor

cjihrig commented Jan 20, 2015

Now that we're a few releases in, is there anything left to do here?

This issue was closed.
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

6 participants