Skip to content
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

set new minimum supported NodeJS version to 18 in package.json engines field #191

Open
thescientist13 opened this issue Feb 6, 2025 · 0 comments · May be fixed by #192
Open

set new minimum supported NodeJS version to 18 in package.json engines field #191

thescientist13 opened this issue Feb 6, 2025 · 0 comments · May be fixed by #192
Assignees
Labels
0.17.0 breaking enhancement Improvement to existing functionality

Comments

@thescientist13
Copy link
Member

thescientist13 commented Feb 6, 2025

Was noticing as part of #190 that our current minimum NodeJS version is set to >=14 and while that technically might be supported, using NVM I was not able get v14 to install locally

I tried testing with v16 but it failed a couple of our test cases because of the lack of fetch and usage of import attributes, and so while not technically an issue with WCC, it would be nice to know that everything works.

Given that even Node 18 is EOL at present, I don't think there's any harm in at least dropping support for everything except >=18.
Image

@thescientist13 thescientist13 added breaking enhancement Improvement to existing functionality labels Feb 6, 2025
@thescientist13 thescientist13 self-assigned this Feb 6, 2025
@thescientist13 thescientist13 moved this to 🏗 In progress in [WCC] General Activities Feb 6, 2025
@thescientist13 thescientist13 changed the title set new minimum NodeJS version to 18 in package.json engines field set new minimum supported NodeJS version to 18 in package.json engines field Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.17.0 breaking enhancement Improvement to existing functionality
Projects
Status: 🏗 In progress
Development

Successfully merging a pull request may close this issue.

1 participant