Skip to content

Conversation

@stevenvachon
Copy link
Contributor

Closes #1.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about using process.release nodejs/node#493 to support io.js also?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, that's pretty new. They're not even sure yet where to put it and I don't see any examples of what its value would look like either. However, yes, supporting this would be a great idea when it's available.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That new process.release Object should no longer be necessary now that io.js and Node.js have merged: http://www.infoq.com/news/2015/05/nodejs-iojs

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, that new stuff was added to io.js v3.0.0, but what good is it to us when io.js is officially Node.js now?

@fengmk2
Copy link
Member

fengmk2 commented Aug 6, 2015

+1

@fengmk2
Copy link
Member

fengmk2 commented Aug 6, 2015

landed 66c8d4b

@fengmk2 fengmk2 closed this Aug 6, 2015
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

Successfully merging this pull request may close these issues.

os name

2 participants