Post

reminder that @nuxt.com doesn’t commit to support specific versions of node - we commit to supporting active and maintenance node versions on a rolling basis 👉 practically that means we may bump a dependency that is incompatible with an eol node version in a patch

Do you drop support for Node majors in a patch?

That wasn't my question. I'm not implying this is wrong, it's a genuine question. Was e.g. Node 20 supported last month and not this month?

i.e. will this be changed in a patch: github.com/nuxt/nuxt/bl...

yes, as of today node isn’t supported for any nuxt version, no matter what engines.node says (engines.node isn’t a promise of support, it’s descriptive. in nuxt’s case it is largely based on the requirements of our dependencies)

I'm not sure how that fits with your original post, but I am in favour of dropping support for versions in a patch as soon as they're EOL. We should probably do that for Astro.

`engines` definitions are meant to "specify the version of <engine> that your stuff works on". You really shouldn't distribute a definition if you don't support it. That said, if you're trying to gate the engine requirements of your transitive deps from consumers then you should probably own that.