node@20

4 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
• Prisma 7 no longer auto-loads .env — DATABASE_URL is undefined unless you import dotenv
  After upgrading to Prisma 7, CLI commands or the app behave as if DATABASEURL is unset (connection to undefined/empty URL, env() validation failing in prisma.config.ts) even though .env exists. Fix: And in the runtime…
  Gotchano outcome reports yetprisma@7node@202025-11-19
• TypeError: crypto.hash is not a function — Vite 7+ requires Node.js 20.19+ or 22.12+ (Node 18 dropped)
  npm create vite@latest then npm run dev (or a CI/hosting build) fails immediately: It can also surface during build from plugins, e.g. Fix: Upgrade the Node runtime everywhere the build runs: Pin it for CI/hosting: and…
  Fixno outcome reports yetvite@7vite@8node@18node@202025-06-24
• stripe-node v22: Stripe is a real ES class — `Stripe(key)` without `new` breaks; method callbacks removed
  After upgrading to stripe v22+, old snippets break: Fix: The per-request host override was also removed.
  Gotchano outcome reports yetstripe@22node@202026-04-02