Allow node@^16.10.0 instead of ^16.13.0

[kirillgroshkov]

🚀 Feature Proposal

Same reasoning as jestjs/jest#12754

People are using 16.10.0 to avoid severe memory leaks that happen since 16.11.0.

Everything else is expected to just work, so it's only an engines field change away in package.json.

Motivation

 

Example

Otherwise it fails when trying to install it with yarn, like this:

[3/5] 🚚  Fetching packages...
error ts-jest@28.0.0: The engine "node" is incompatible with this module. Expected version "^12.13.0 || ^14.15.0 || ^16.13.0 || >=17.0.0". Got "16.10.0"
error Found incompatible module.

[kirillgroshkov]

And while we're at it, ^17.0.0 is end-of-life, suggested line is:

^12.13.0 || ^14.15.0 || ^16.10.0 || ^18.0.0

Node.js 12 is end-of-life too, so, even better line:

^14.15.0 || ^16.10.0 || ^18.0.0

[ahnpnl]

I think we should stick to what Jest asks for:) PR is welcome

[kirillgroshkov]

Fair. Will come up with a PR shortly!

[SimenB]

(v17 isn't EOL until June 1, see https://github.com/nodejs/Release)