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

Why process.versions still use the node ? #396

Closed
Pana opened this issue Jan 14, 2015 · 4 comments
Closed

Why process.versions still use the node ? #396

Pana opened this issue Jan 14, 2015 · 4 comments

Comments

@Pana
Copy link

Pana commented Jan 14, 2015

versions:
{ http_parser: '2.3',
node: '1.0.1',
v8: '3.31.74.1',
uv: '1.2.0',
zlib: '1.2.8',
ares: '1.10.0-DEV',
modules: '42',
openssl: '1.0.1k' }

@jamescostian
Copy link

If you're using a module that pays attention to the versions (e.g. NPM, when you install something that wants "node": ">=0.8") and it doesn't see Node, it might panic and throw errors

@zauguin
Copy link

zauguin commented Jan 14, 2015

Maybe both should be included, otherwise it could get messy when nodeJS reaches 1.0.0: {..., node: '0.11.0+compatible, io: '1.0.1', ...} anyone?

@bajtos
Copy link
Contributor

bajtos commented Jan 14, 2015

Maybe both should be included

+1

There should be a way how to detect whether the runtime is Node.js or io.js

@dougwilson
Copy link
Member

See #253 (comment) and #253 (comment)

@cjihrig cjihrig closed this as completed Jan 15, 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

No branches or pull requests

6 participants