Why is Node v8.x required?

[niftylettuce]

https://github.com/amilajack/eslint-plugin-compat/blob/master/package.json#L70

[ljharb]

it was done in #218, presumably to be able to transpile to a later target.

[amilajack]

It's not really required. As a maintainer I didn't want to handle bug reports for older versions. But if you need support for older versions I'll lower the node version requirement. Should be as simple as a babel-preset-env target change and engines version change

[niftylettuce]

If we could remove the requirement in engine of package.json that would be great

[ljharb]

eslint itself requires node 4, and babel 7 requires node 4 as well i think - so removing it isn't an option, but dropping it down to 4 should be.

[niftylettuce]

Makes sense, ty for lmk

…

On April 25, 2019 11:09:01 PM UTC, Jordan Harband ***@***.***> wrote: eslint itself requires node 4, and babel 7 requires node 4 as well i think - so removing it isn't an option, but dropping it down to 4 should be. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #224 (comment)

[amilajack]

Yarn supports >=8 so we're locked to that same semver because of users who install this lib with yarn

[ljharb]

Um, that’s not how it works - npm users aren’t locked to that, and older versions of yarn won’t require node 8.

An eslint plugin should always support every node version eslint supports.

[amilajack]

Semver package requires node >=10

[ljharb]

The latest version does, but there’s no reason we need to use > v6 - v7 only changes prerelease logic.

Let’s stop looking for excuses to drop support, and try to support as far back as possible?