-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add back support for node 16.10 #476
Comments
We officially only support actively maintained LTS releases. This is what is indicated by having 16.13 in |
Thank you for considering and for the explanation. Not sure about npm, but yarn fails to install on the engines requirement. For anyone using yarn and looking for a workaround: |
Thanks for that comment. It's been a while since I've used Yarn and I forgot this behavior is different than npm. For npm, it just prints a warning, there's no ignore parameter needed, e.g.
It's worth noting, that a bunch of the latest Jest dependencies behave the same way,
|
I think we can do the same here as in jestjs/jest#12754 and kulshekhar/ts-jest#3495 just so people don't have to supply a flag (or ignore warnings). |
I don't object. I don't pay much attention to |
I have node
|
Node 16 (and even Node 14) supports optional chaining, so you're not using that. That said, this is not the correct issue (or even repository) to report your issue. |
Feature Request
Description:
Please add back support for node 16.10 into the
package.json
engines
field.the latest versions of jest-extended cannot be used when you're trying to avoid high memory consumption by jest in node v 16.11+ as described in jestjs/jest#11956.
This concerns jest-extended
^2.1.0
as well as^3.0.0
.Possible solution:
Lower engines requirements for node to
16.10
from16.13
inpackage.json
The text was updated successfully, but these errors were encountered: