cli: compatibility with node v21

[juweeks]

Describe the feature

synthing with node v21 results in RuntimeError: Error: ENOENT: no such file or directory, open 'cdk.out/tree.json'

Use Case

node v21 was released 10/2023 and is the latest stable version

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.113.0

Environment details (OS name and version, etc.)

mac 13.6.1

[gordinmitya]

I can confirm this issue.
Just encountered on Ubuntu 23.10 with node v21.3.0 and cdk 2.113.0 (build ccd534a)

Stacktrace

jsii.errors.JavaScriptError: 
  @jsii/kernel.RuntimeError: Error: ENOENT: no such file or directory, open 'cdk.out/tree.json'
      at Kernel._Kernel_ensureSync (/tmp/tmpgc0na0y3/lib/program.js:10491:23)
      at Kernel.invoke (/tmp/tmpgc0na0y3/lib/program.js:9855:102)
      at KernelHost.processRequest (/tmp/tmpgc0na0y3/lib/program.js:11699:36)
      at KernelHost.run (/tmp/tmpgc0na0y3/lib/program.js:11659:22)
      at Immediate._onImmediate (/tmp/tmpgc0na0y3/lib/program.js:11660:46)
      at process.processImmediate (node:internal/timers:478:21)

Downgrading Node.js to v20.10.0 resolved the issue.

[khushail]

@juweeks , could you please share the specific scenario (repro code) where you faced this issue?

[juweeks]

@juweeks , could you please share the specific scenario (repro code) where you faced this issue?

There really isn't a specific scenario here.

1. Synthed multiple CDK apps using lower node version and worked.
2. Upgraded node n stable and it installed node v21.
3. Tried synthing multiple CDK apps again on the upgraded node and got the runtime error on each synth.
4. Downgraded to node v20 and synths worked again.

[pahud]

@juweeks CDK is not fully tested in node v21 and we suggest to go to v20 instead.

[juweeks]

understood. that's why this is a feature request and not a bug report. would like to request that cdk be compatible with v21 if it's neither on a roadmap nor previously requested.

[rix0rrr]

We are unlikely to work on this since 20 and 22 are both stable Node versions and 21 is not.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.