-
Notifications
You must be signed in to change notification settings - Fork 45
fix(build): Support node.js 22 #2104
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
Conversation
bfd1026 to
3372485
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2104 +/- ##
============================================
+ Coverage 81.48% 81.61% +0.12%
Complexity 455 455
============================================
Files 537 537
Lines 16823 17000 +177
Branches 3302 3538 +236
============================================
+ Hits 13708 13874 +166
- Misses 2856 2867 +11
Partials 259 259 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
when using Node 22, I have a compilation error locally with using Node.js v22.14.0 |
3372485 to
a7904f7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
build fine with Node 22 and works with VS Code extension built with Node 20
Starting with node.js 21, the `--loader` is no longer valid, making the build to fail. This commit transform the `.mts` file to a `.mjs` so we don't need to use the `typescript` loader and it also removes the warning generated by importing JSON files. The node.js version for the github actions is also updated. The JSON import problem was handled thanks to @petersem nodejs/node#51347 (comment) fix: KaotoIO#1936 relates: nodejs/node#51347
|
Context
Starting with node.js 21, the
--loaderis no longer valid, making the build to fail.This commit transforms the
.mtsfile to a.mjsfile so we don't need to use thetypescriptloader. It also removes the warning generated by importing JSON files.The JSON import problem was handled thanks to @petersem nodejs/node#51347 (comment)
fix: #1936
relates: nodejs/node#51347