RFC: Raise the minimum Node.js version to 22 in the next major #2658

Idea

Raise the minimum Node.js version to 22 in the next major release of the Faust.js packages.

Reasoning

Node.js 20 reached end of life in April 2026 and no longer gets security fixes. #2653 stops testing it in CI, but the packages still declare engines.node: >=18, so npm doesn't warn anyone installing on an unsupported version. Ecosystem breakages now land only on Node 20. One example: a partial vitest release on Oct 15, 2026 crashed npm 10.8, the npm that ships with Node 20, on a fresh install of our examples, which needed a temporary pin (#2651).

Raising engines is a breaking change, so it waits for a major release:

Sites that need to stay on Node 20 keep working on core and cli 3.x and blocks 6.x. The FaustWP plugin isn't affected.

Steps

If agreed:

• Announce the change in Discussions ahead of the release (Faust.js will require Node.js 22 or newer in its next major release #2672)
• Note the upcoming minimum in the changelog of the last 3.x and 6.x releases (core and cli 3.6.0, blocks 6.1.14)
• Set engines.node to >=22 in core, cli and blocks, and in the examples (feat!: require Node.js 22 or newer #2670)
• Release it as a breaking change (feat!: title or a Release-As footer)
• Remove the temporary vitest override from the examples if it's still there (fix(examples): pin vitest so the examples install on Node 20 #2651)