Is Node 18 really required?

[axelboc]

pnpm is telling me that my Node version (16) is incompatible with the one specified in galex' package.json. I don't mind upgrading in some evergreen projects, but in others it will take more time and convincing...

I assume this is a development requirement, not a requirement of the galex library per se? Would it be possible to update the package.json published to NPM to remove the engines field, maybe?

[ljosberinn]

hey, good point. I initially wanted to upgrade .. I think read-pkg-up to latest but then realized while I can install and import it, it'll still have to run in a CJS context due to ESLint itself, so I downgraded again, but kept the Node version since it's LTS: https://nodejs.org/en

I'll check whether I can drop the field and republish, yea.

[ljosberinn]

ah semantic-release wants it too

[ljosberinn]

semantic-release wants this since v20 already, meaning the Node 18 requirement isnt even new, but from January 👀

[ljosberinn]

I'll downgrade to the latest non-ESM version regardless as it's dev/CI related only however

[axelboc]

Awesome, thanks for the reactivity as always 😊