-
Notifications
You must be signed in to change notification settings - Fork 246
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
Incorrect Node22 warnings on load #4581
Comments
False alarm. The warnings are due to an old version of CDK: epolon@bcd07455aba8 ~
❯ npx --yes [email protected] --version [16:52:40]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! This software has not been tested with node v22.5.1. !!
!! Should you encounter odd runtime issues, please try using one of the supported release before filing a bug report. !!
!! !!
!! This software is currently running on node v22.5.1. !!
!! As of the current release of this software, supported node releases are: !!
!! - ^20.0.0 (Planned end-of-life: 2026-04-30) !!
!! - ^18.0.0 (Planned end-of-life: 2025-04-30) !!
!! !!
!! This warning can be silenced by setting the JSII_SILENCE_WARNING_UNTESTED_NODE_VERSION environment variable. !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2.139.1 (build b88f959)
epolon@bcd07455aba8 ~
❯ npx --yes [email protected] --version [16:52:46]
2.140.0 (build 46168aa) Node 22 support was added in |
This issue is now closed. Comments on closed issues are hard for our team to see. |
1 similar comment
This issue is now closed. Comments on closed issues are hard for our team to see. |
Using the CDK cli with Node22 produces the following warning:
It happens as soon as the CDK cli is loaded, see: https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk/lib/cli.ts#L2
However, this is actually inaccurate, because support for Node22 was added a while back, and it exists in our testing matrix as well. For example:
Looks like there's either a bug in how we determine tested versions, or we missed something when adding node 22 support.
The text was updated successfully, but these errors were encountered: