Post

daniel r(ooooooh) at jsconf mx 🇲🇽
@danielroe.dev

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

Node.js@nodejs.org

Reminder: Node.js v20 is end-of-life (EOL) today. Upgrade + get security support for EOL versions here: https://nodejs.org/en/about/eol

nodejs.orgNode.js — End-Of-LifeUnderstand Node.js End-of-Life, what it means for security, tooling, and compliance, plus EOL version details and commercial support options.

3 reposts64 likes

Matt Kane
@mk.gg

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?

daniel r(ooooooh) at jsconf mx 🇲🇽
@danielroe.dev

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)

Lucie
@lihbr.com

Way to go, updating Node runtime regularly is critical for security housekeeping

Artem Zakharchenko
@kettanaito.com

I generally find it surprising how many developers don't realize they can just pin the dependency version. Especially when something unintentionally broke. Open source literacy is rather low.