EnvGap
Allow node@^16.10.0 instead of ^16.13.0
envgap__kulshekhar__ts-jest-3494
01 / FAILURE SIGNATURE
As reported upstream
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"
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
ade95354d2c1c2918c4f272e43823b71f9210229- Manifest
package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
kulshekhar/ts-jest #3494 · read the original issue
### 🚀 Feature Proposal Same reasoning as https://github.com/facebook/jest/pull/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. ```
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]