You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think, we need to change binary file names for io.js with fallback to node.js. For example, when i trying to compile io.js i'm replacing original node version. But, i have some problem, if i want use io.js and node.js in one time.
I am pleased to see your valuable contribution to this project. Would you
please mind answering a couple of questions to help me classify this submission
and/or gather required information for the core team members?
Questions:
Issue-only Does this issue happen in core, or in some user-space
module from npm or other source? Please ensure that the test case
that reproduces this problem is not using any external dependencies.
If the error is not reproducible with just core modules - it is most
likely not a io.js problem. Expected: yes
Which part of core do you think it might be related to? One of: tls, crypto, buffer, http, https, assert, util, streams, smalloc, cluster, child_process, dgram, c++, docs, other (label)
Which versions of io.js do you think are affected by this? One of: v0.10, v0.12, v1.0.0 (label)
Please provide the answers in an ordered list like this:
Answer for the first question
Answer for the second question
...
Note that I am just a bot with a limited human-reply parsing abilities,
so please be very careful with numbers and don't skip the questions!
In case of success I will say:...summoning the core team devs!.
In case of validation problem I will say:Sorry, but something is not right here:.
I think, we need to change binary file names for io.js with fallback to node.js. For example, when i trying to compile io.js i'm replacing original node version. But, i have some problem, if i want use io.js and node.js in one time.