RepoJournal
Node.js

@nodejs

The Node.js runtime — every backend team's CVE source of truth

Pick a date

  1. Tue 5 may
  2. Wed 6 may
  3. Thu 7 may
  4. Fri 8 may
  5. Sat 9 may
  6. Sun 10 may
  7. Mon 11 may
  8. Tue 12 may
  9. Wed 13 may
  10. Thu 14 may
  11. Fri 15 may
  12. Sat 16 may
  13. Sun 17 may
  14. Mon 18 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

COREPACK DROPS NODE 20 AND 25 SUPPORT, UNDICI 8.3.0 SHIPS POOL FIX

By RepoJournal · Filed · About Node.js

Corepack is breaking backward compatibility by ending support for Node.js 20 and 25, while requiring NODE_USE_ENV_PROXY for proxy functionality going forward.

Corepack's new engine support matrix [1] [2] marks a significant shift in maintenance strategy, dropping two actively-used versions and moving to built-in proxy support that requires explicit environment configuration. This is a forcing function for teams still on Node 20 to plan their migration timeline now. Undici 8.3.0 landed this morning [3] with a critical fix that preserves pool capacity after removing stale clients [3], addressing a connection stability issue that affected production workloads. The release also fixes a race condition in test suites on Windows [4] where listeners registered after connection initiation could miss events. Over on nodejs.org, the dev team merged a lint toolchain refresh [5] bumping ESLint to 10.2.1, TypeScript-ESLint to 8.59.1, and Prettier to 3.8.3, plus React component library updates [6] to 19.2.6. Playwright test infrastructure got a Windows fix in 1.59.1 [7] that restores codegen and UI functionality after a console window regression.

Action items

References

  1. [1] chore(deps): bump engine support matrix ↗ nodejs/corepack
  2. [2] chore(deps): bump engine support matrix (#831) nodejs/corepack
  3. [3] v8.3.0 ↗ nodejs/undici
  4. [4] fix: register connect listener before initiating requests in close-and-destroy test ↗ nodejs/undici
  5. [5] meta: bump the lint group across 1 directory with 5 updates ↗ nodejs/nodejs.org
  6. [6] meta: bump the react group across 1 directory with 2 updates ↗ nodejs/nodejs.org
  7. [7] meta: bump @playwright/test from 1.58.2 to 1.59.1 ↗ nodejs/nodejs.org

FAQ

What changed in Node.js on May 15, 2026?
Corepack is breaking backward compatibility by ending support for Node.js 20 and 25, while requiring NODE_USE_ENV_PROXY for proxy functionality going forward.
What should Node.js teams do about it?
Plan Node.js version migration away from 20 and 25 before updating Corepack • Update Undici to 8.3.0 to fix pool capacity handling • Sync lint dependencies in nodejs.org workflow (ESLint 10.2.1, TypeScript-ESLint 8.59.1)
Which Node.js repositories shipped on May 15, 2026?
nodejs/corepack, nodejs/undici, nodejs/nodejs.org

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.