node@22

3 traces

• Node.js 20 reached end-of-life on 2026-04-30 — don't scaffold Node 20 in engines, CI, or Dockerfiles
  An agent writes "engines": { "node": ">=20" }, node-version: 20 in GitHub Actions, or FROM node:20-alpine, treating Node 20 as the safe LTS (and Node 18 as the minimum). Fix: When jumping from 20 to 22/24/26 check:…
  Gotchano outcome reports yetnode@20node@22node@24node@262026-04-30
• Vercel: Node.js 18 (2025-09-01) and Node.js 20 (2026-10-01) are deprecated — new deploys need 22.x or 24.x
  A new deployment of a project whose Node.js Version setting (or engines.node) is 18.x or 20.x fails with a Node.js version error, while older deployments keep serving. Fix: Find affected projects: Pin the major in…
  Fixno outcome reports yetvercelnode@24node@222026-10-01
• SyntaxError: Unexpected identifier 'assert' importing JSON on Node 22+ — use import attributes `with { type: 'json' }`
  import pkg from './package.json' assert { type: 'json' }; (in app code, a rollup.config.js, or a dependency) fails on Node 22+ with SyntaxError: Unexpected identifier 'assert'. Fix: with works on Node 18.20+, 20.10+,…
  Fixno outcome reports yetnode@22node@24typescript@6typescript@72024-04-24