OSS Feed: 2026-03-26

@acdlite — Andrew Clark

Active on React and Next.js discussions:

@gaearon — Dan Abramov

Busy day fielding React issues — 4 comments across core React:

@sebmarkbage — Sebastian Markbåge

A quiet day. 🌿

@tannerlinsley — Tanner Linsley

A quiet day. 🌿

@leerob — Lee Robinson

  • Reviewed a docs contribution to Fastify: docs: update Vercel section — keeping Vercel's deployment docs accurate across the ecosystem

@timneutkens — Tim Neutkens

The most active engineer today — deep in Next.js performance work:

PR opened:

Performance review blitz — Tim reviewed a series of micro-optimization PRs:

Also active on:

@bvaughn — Brian Vaughn

PR opened:

Also commented on the React useState with class issue alongside Dan Abramov.

@t3dotgg — Theo Browne

@TkDodo — Dominik Dorfmeister

Splitting time between TanStack Query and Sentry:

TanStack Query:

Sentry (day job):

Also reviewed an upstream fix: node-http-proxy: Don't break on invalid headers

@phryneas — Lenz Weber-Tronic

Active on Apollo Client:

@markerikson — Mark Erikson

Data unavailable due to GitHub API rate limiting. 🚫

@kettanaito — Artem Zakharchenko

Data unavailable due to GitHub API rate limiting. 🚫

Today's Highlight

Tim Neutkens' Next.js Performance Sprint 🏎️ — Tim reviewed an impressive batch of micro-optimization PRs targeting Next.js runtime performance: faster URL checks with charCodeAt, lazy-loading watchpack in production, caching regex patterns, and deferring instrumentation. These small wins compound into meaningful cold-start and request-handling improvements. The Next.js team is clearly in "squeeze every millisecond" mode heading into the next release cycle.

Also notable: Dan Abramov and Brian Vaughn crossing paths on the useState with class initial state issue — a fun throwback to React internals discussions from the old guard.