-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Is it time to drop Node.js 0.10 support (in 2.x) #832
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
Comments
#740 works in 0.10 actually. I think #808 is the only one that is borked in 0.10, but I also think #808 does not add any new failures; I think the error happens only if you access the prototype, which is already broken. In any case, my 👍 indicates support because I think it's good to discourage use of EOL runtimes, but not sure if it's necessary to drop support given the above. |
In any case, think this part of the readme can be removed 😆:
|
I found this tweet from the NPMer who posts stats sometimes. Looks like maybe it's a bit early, I haven't used 0.10 in a long long time though
I noticed that the other day too!😆 |
There's a more recent version here. There's also some other things to consider on the numbers. |
Some interesting discussion going on here related to that: travis-ci/travis-ci#6659 |
Here are some more recent data, I feel that it's time to drop both Node.js 0.10 and also Node.js 0.12 since 0.12 has a lower adoption rate then 0.10. Both is end of life and there doesn't seem to be that many people using it... https://docs.google.com/spreadsheets/d/1J6TxXIfGOqV9cx1qEFGSXHCma4JHfKPzlsMWfbGmDbE/edit#gid=0 |
@LinusU Awesome! Where did you get the Node usage data from? |
As far as I know, that document is maintained by npm. Got it from expressjs/discussions#11 😄 |
Uh oh!
There was an error while loading. Please reload this page.
Official support for Node.js 0.10 will cease after tomorrow. We currently have a few issues with 0.10 as well, which currently hinders the merging of #740 and #808.
Would anyone be sad by seeing 0.10 support go?
Is it, as module authors, even good to continue to support an end of life version of Node?
Any input is appreciated!
(note that this will only happen in a major version, v 1.x will continue to work with 0.8 and 0.10 forever)
The text was updated successfully, but these errors were encountered: