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.

Node 15 isn't supported for v8?

See original GitHub issue

Updating dependencies for my project, and compliance is failing when testing on node 15 due to espree v8:

error espree@8.0.0: The engine "node" is incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || >=16.0.0". Got "15.14.0"

Is there a reason for this? Will it actually not work when running on node 15?

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

silverbucketcommented, Aug 17, 2021

Thanks everyone, yes we’ve decided to remove testing for 15, and going forward we will add compliance checks and integration testing for odd versions only as long as they are active, remove them as soon as the next LTS is released.

1reaction

bmishcommented, Aug 17, 2021

It’s pretty standard practice among NPM packages to only support the active LTS versions of Node (currently, that’s Node 12, 14, 16, and anything higher for flexibility). Many other popular NPM packages have already moved to the same list of supported Node versions as ESLint v8.

My personal advice for you:

Regarding running linting: technically, it’s likely sufficient to run your internal project linting against your primary Node version only (which it sounds like is Node 16).

Regarding running tests in general:

If your project is an app running on Node 16, then you only really need to test on Node 16 at this point (you could start testing higher versions once they come out).
If your project is a library, then you would want to test against any Node versions it supports.