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

Is it time to drop Node.js 0.10 support (in 2.x) #832

Closed
LinusU opened this issue Oct 30, 2016 · 8 comments
Closed

Is it time to drop Node.js 0.10 support (in 2.x) #832

LinusU opened this issue Oct 30, 2016 · 8 comments

Comments

@LinusU
Copy link
Collaborator

LinusU commented Oct 30, 2016

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)

@zbjornson
Copy link
Collaborator

#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.

@zbjornson
Copy link
Collaborator

In any case, think this part of the readme can be removed 😆:

Tested with and designed for:

node 0.4.2
cairo 1.8.6
For node 0.2.x node-canvas <= 0.4.3 may be used, 0.5.0 and above are designed for node 0.4.x only.

@chearon
Copy link
Collaborator

chearon commented Oct 31, 2016

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

In any case, think this part of the readme can be removed

I noticed that the other day too!😆

@jdalton
Copy link

jdalton commented Nov 7, 2016

There's a more recent version here. There's also some other things to consider on the numbers.
Accounting for that it looks like 0.10 use is < 10% now.

@LinusU
Copy link
Collaborator Author

LinusU commented Nov 7, 2016

Some interesting discussion going on here related to that: travis-ci/travis-ci#6659

@LinusU
Copy link
Collaborator Author

LinusU commented May 3, 2017

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

@jdalton
Copy link

jdalton commented May 4, 2017

@LinusU Awesome! Where did you get the Node usage data from?

@LinusU
Copy link
Collaborator Author

LinusU commented May 4, 2017

As far as I know, that document is maintained by npm. Got it from expressjs/discussions#11 😄

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

4 participants