OSS Feed: 2026-04-07

@kettanaito — Artem Zakharchenko

Heavy MSW momentum: two draft breaking-change PRs landed for MSW 3.0feat!: 3.0 and feat!: msw/graphql, graphql as an optional peer dependency. He also closed a cluster of foundational PRs around the network-source architecture, @msw/url, browser lifecycle fixes, and Windows CI support.

PRs opened:

Code reviews & comments:

  • Engaged on the GraphQL optional peer dependency PR and related MSW merges
  • Commented on feat: implement msw plugin in openapi-ts
  • Closed discussion threads on older MSW issues including connection-refused behavior and React Native + Axios mocking
  • Resolved Improve API of the clear method in async-history-stack

@timneutkens — Tim Neutkens

Comments:


@TkDodo — Dominik Dorfmeister

Comments:


@tannerlinsley — Tanner Linsley

Comments:

  • Active TanStack Query triage across several closed historical PRs, including SSR improvements, refetch-interval fixes, infinite-query cursor rebuilds, and sample/docs cleanups — signals steady maintenance on long-tail community contributions.

@leerob — Lee Robinson

Comments:


@bvaughn — Brian Vaughn

Comments:


@acdlite — Andrew Clark

A quiet day. 🌙


@gaearon — Dan Abramov

A quiet day. 🌙


@sebmarkbage — Sebastian Markbåge

A quiet day. 🌙


@phryneas — Lenz Weber-Tronic

A quiet day. 🌙


@t3dotgg — Theo Browne

A quiet day. 🌙


@markerikson — Mark Erikson

A quiet day. 🌙


Today's Highlight

🔥 MSW 3.0 is taking shape — Artem opened draft PRs for a major MSW release and optional GraphQL packaging, while landing the supporting refactors (network architecture, URL layer, browser worker lifecycle). If you rely on MSW, watch those threads: peer dependency and import surface changes tend to ripple through test suites.

Runner-up: Next.js stream + Edge boundaries — Tim’s activity on fork points for Node streams and Edge-safe node:stream imports is the kind of plumbing work that prevents subtle production/runtime mismatches as the framework keeps pushing hybrid rendering.