Closed gabalafou closed 2 months ago
We are not using 18.x
, we have "node": ">=18.0.0"
in our package.json
which, depending on when one last updated/created their env should be on the latest point release of node (for example right now should be on 22.x
)
I think the action here would be to bump the minimum version to 22
based on the Node EOL calendar https://endoflife.date/nodejs (technically we could go to 20
but everything seems to work on 22
)
Left a comment in #415 we can address this in that PR directly or do a stack of PRs
Feature description
We are currently using Node 18
Value and/or benefit
Node is already at version 22, so we're two versions behind.
Anything else?
No response