Why does this eslint-plugin insists on npm =>7

[stefanlivens]

We're (or at least our CI/CD environment) is still on node14+npm6. This trips up our CI-engineers to which we need to explain every time it is not a big deal.

npm WARN notsup Unsupported engine for eslint-plugin-testcafe-community@1.2.6: wanted: {"node":">=10.24","npm":">=7.0.0"} (current: {"node":"14.17.0","npm":"6.14.13"})
npm WARN notsup Not compatible with your version of node/npm: eslint-plugin-testcafe-community@1.2.6

eslint itself isn't that strict.

[codejedi365]

You're right. There's no requirement within the plug-in for npm@7. I forgot the engines is checked during a production install.

I only put it in there to define the dev environment which requests NPMv7 since it has a bunch of changes related to package-lock. And I didn't want to keep rebuilding a lock file.

Thank you for bringing this error to my attention, I will have it removed today.

[github-actions]

🎉 This issue has been resolved in version 1.2.8 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀