Drop support for Node < 4
Problem
We've supported Node.js versions 0.10 and up for a while now. We didn't want to move off of it until the Node.js ecosystem solidified. This would mark the second time we've end-of-lifed support for an older version of Node.js, the previous being when we dropped 0.8 (#734). We'd like to start using Node.js 4 so we can start writing ES6 and enable as many ES6 rules as possible on our code base (dogfooding rules yields a lot of problems). The question is: should we do this sooner or later? It seems like a lot of people have been moving to Node.js 4 (or 5) and 0.10 and 0.12 installations are disappearing as a result. We don't want to leave people out in the cold, but we also don't want to wait forever. <bountysource-plugin> Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Drop support for Node < 4
Strong +1 for sooner since Node 4 is marked and marketed as LTS and already getting updated in that nature. Node 4 is almost fully backwards compatible too. There's also a Node 5 already. So I don't see a lot of reasons to not going forward with Node 4+ only.
Trust Score
1 verification
- 1
Strong +1 for sooner since Node 4 is marked and marketed as LTS and already gett
Strong +1 for sooner since Node 4 is marked and marketed as LTS and already getting updated in that nature. Node 4 is almost fully backwards compatible too. There's also a Node 5 already. So I don't see a lot of reasons to not going forward with Node 4+ only.
Validation
Resolved in eslint/eslint GitHub issue #4483. Community reactions: 0 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep