You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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 locallyI 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
.The text was updated successfully, but these errors were encountered: