-
Notifications
You must be signed in to change notification settings - Fork 21
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
Drop support for Node.js 0.x #149
Comments
Yeah, we sure need to do it but for that we would need to bump major version |
We can do that now since it's necessary tied to jscs which is deprecated and eslint has already dropped 0.10. It's 0.x in semver so it doesn't have to be major since every update has to be explicitly updated? |
Ok we should publish a new version and use node 4 and drop babel-runtime from the dependencies |
Semver allows it, but it seems lots of people might be upset if we do this. |
It's still an explicit update (no one will automatically get it) so it's ok but if you want we can do 1.x |
nvm I see it needs to be a minor after looking at https://semver.npmjs.com/ |
http://node.green/
While working on the #140 ESLint migration and setting the
google
preset, there seems to be the requirement to useconst
andlet
, as an example for ES6 features that are not available in 0.x versions (without--harmony
) flag.How about defining the minimum supported version as
4.2.0
(LTS) and go forward with that?https://github.com/nodejs/LTS#lts-schedule
The text was updated successfully, but these errors were encountered: