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

STREAM BACKPRESSURE FIX PREVENTS DATA DUPLICATION IN PIPETO

By RepoJournal · Filed · About Node.js

Node core patched a critical bug in pipeTo() that duplicated chunks when writers returned false during backpressure, causing output like 'abcdcd' instead of 'abcd'.

The fix [1] [2] corrects how pipeTo() interprets false returns from PushWriter in block backpressure mode. Previously, the code mistakenly retried accepted data asynchronously, creating duplicates. Now it properly waits for drain instead. This lands alongside stream efficiency improvements [3] [4] that clean up unnecessary type checking in the stream pipeline. On the documentation front, doc-kit shipped HTML generation for index and 404 pages [5], improving static site output. Meanwhile nodejs.org deployed two critical fixes: a sidebar layout bug that clipped navigation items on scroll [6] [7], and a content migration refresh that reorganizes the blog post timeline [8] [9]. The website also switched queue handling away from Durable Objects to memoryQueue for better skew protection [10].

Action items

References

  1. [1] stream: avoid retrying accepted pipeTo writes ↗ nodejs/node
  2. [2] stream: avoid retrying accepted pipeTo writes nodejs/node
  3. [3] stream: remove unnecessary check nodejs/node
  4. [4] streams: remove unnecessary check ↗ nodejs/node
  5. [5] feat(web): add all, index, and 404 generation ↗ nodejs/doc-kit
  6. [6] fix: sidebar last items hidden behind header on scroll (#8852) nodejs/nodejs.org
  7. [7] fix: sidebar last items hidden behind header on scroll ↗ nodejs/nodejs.org
  8. [8] Content(migrations): update ↗ nodejs/nodejs.org
  9. [9] Content(migrations): update (#8881) nodejs/nodejs.org
  10. [10] chore(open-next): avoid the use of DurableObjects by using `queueCache` with `memoryQueue` instead ↗ nodejs/nodejs.org

FAQ

What changed in Node.js on May 17, 2026?
Node core patched a critical bug in pipeTo() that duplicated chunks when writers returned false during backpressure, causing output like 'abcdcd' instead of 'abcd'.
What should Node.js teams do about it?
Verify pipeTo() behavior in production if you pipe to backpressured writers • Test your stream pipelines for duplicate chunk output after next node release • Review nodejs.org sidebar rendering if you customize navigation layout
Which Node.js repositories shipped on May 17, 2026?
nodejs/node, nodejs/doc-kit, 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.