Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Decide which Node versions ESLint 6 should support

See original GitHub issue

This issue is a follow-up from today’s TSC meeting. The TSC decided that ESLint 6 will drop support for Node 6, with the precise Node version support TBD.

Based on https://github.com/eslint/eslint/issues/11022, it seemed like the consensus was that we should pick Node version requirements based on specific features we might want to use in ESLint, rather than just picking the latest Node versions as we did for v5.x. (However, not a lot of team members have chimed in on https://github.com/eslint/eslint/issues/11022 – feel free to add to that discussion, particularly if you disagree with that general approach.) I’ve mostly gone with that approach, although I’ve also taken into consideration which Node versions users will typically be upgrading to.

We currently support everything above Node 8.10.0 on the Node 8 release line. I don’t think we should tighten that requirement, since AWS Lambda only supports Node 8.10.0. We’ve received a few requests to loosen that requirement with ESLint 5, but I’d rather not do that either since it could be nice to have features like Module.builtinModules and correct require.resolve behavior with the paths argument, both of which were introduced in Node 8.10.0.

I think we should drop support for Node 9, since it’s been at EOL for almost a year.

We currently support all versions of Node 10. There aren’t any features we specifically need in Node 10 aside from the ones that in Node 8, so I’d recommend starting at the first Node 10 LTS release (i.e. ^10.13.0) since this is probably where most users start using Node 10.

Node 11 is going to be EOL in June, so I don’t think too many users will be stuck on old versions of it. As a result, I’d arbitrarily suggest picking the latest version as of now, i.e. 11.10.1.

So I think our Node version support for ESLint 6 should be:

^8.10.0 || ^10.13.0 || >=11.10.1