OSS Feed: 2026-04-01
@TkDodo — Dominik Dorfmeister
The most active engineer today, with major work across TanStack Query and Sentry.
PRs Opened:
- ref: switch from throwing promises to React.use — A significant refactor for TanStack Query's suspense integration, moving from the legacy "throw promises" pattern to the new
React.useAPI. This is a big architectural shift. - ref: update TanStack Query (draft) — Updating TanStack Query in Sentry's codebase.
- fix(ci): let precommit format json files — CI fix for Sentry.
- ref: update TanStack Form — TanStack Form update in Sentry.
Code Reviews & Comments:
- Reviewed fix(build): exclude config files from production DTS rollup in TanStack Query
- Commented on docs(react): add polling guide — improving Query documentation
- Engaged with several older TanStack Query PRs and issues including devtools light mode, infinite query error handling, and exposing the
Querytype - Active on Sentry layout/UI PRs: page paddings alignment, CompositeSelect ClearButton, nav indicator realignment
- Reviewed multi-sort projections in Remeda
@gaearon — Dan Abramov
Comments:
- Bug: Rendered more hooks than during the previous render — Investigating a tricky hooks ordering bug that occurs when a component calls
use(thenable)after hydration in a specific transition scenario. - Bug: ViewTransition with enter/exit hard-crashes iOS Safari — Engaging on a critical ViewTransition crash affecting iOS Safari. Sebastian Markbåge also commented on this one.
@sebmarkbage — Sebastian Markbåge
Comments:
- Bug: ViewTransition with enter/exit hard-crashes iOS Safari — Collaborating with Dan on the ViewTransition iOS Safari crash. Given Sebastian's role as React architecture lead, his involvement suggests this is being taken seriously.
@acdlite — Andrew Clark
Comments:
- Active on several Next.js PRs around the instant navigation / cached navigation feature set:
@phryneas — Lenz Weber-Tronic
Comments:
- No way to set nonce on inline script for CSP — Addressing Content Security Policy challenges in Apollo integrations.
- Add preloadQuery.awaitable() API — Working on a new API for awaiting partial query data in react-router loaders.
- Drop backwards compatibility — Contributing to the GraphQL-over-HTTP spec discussion.
- Enforce global type declaration for
defaultOptions— Type safety improvements in Apollo Client.
@tannerlinsley — Tanner Linsley
Comments:
- Active on TanStack Query issue triage — reviewed and commented on several PRs including fix(types): change return type of removeQueries, Reset failureCount to zero, and fix(types): ReactQueryConfigProvider error type.
@kettanaito — Artem Zakharchenko
Comments:
- Add note about
boundarywitharoundEach— Documentation improvements for MSW. - Meta: Native support for ES Modules — Still engaged in the long-running Jest ESM discussion. This issue has been open since 2019 and remains one of the most important meta-issues in the JS testing ecosystem.
@bvaughn — Brian Vaughn
Comments:
- useDefaultLayout returns a new object each render — Addressing an unstable reference issue in react-resizable-panels, a common React performance pitfall.
@timneutkens — Tim Neutkens
Comments:
- telemetry: set turboFlag correctly — Reviewing a telemetry fix in Next.js.
@leerob — Lee Robinson
Comments:
- chore(scores): update elite 8 scores — Maintaining his March Madness bracket app. 🏀
@t3dotgg — Theo Browne
A quiet day. 🌙
@markerikson — Mark Erikson
A quiet day. 🌙
Today's Highlight
🔥 TkDodo's React.use migration in TanStack Query — The PR switching from throwing promises to React.use is the standout activity today. This represents a fundamental shift in how TanStack Query handles suspense, moving away from the "throw a promise" hack that React Suspense originally relied on, toward the official React.use API. This change signals that the React ecosystem is maturing past its early Suspense patterns and embracing the stable APIs. Keep an eye on this one — it will affect every TanStack Query user running suspense mode.
Also noteworthy: the ViewTransition iOS Safari crash (#35336) drew attention from both Dan Abramov and Sebastian Markbåge, suggesting React's new View Transitions feature has a critical platform compatibility issue that needs resolution before wider adoption.
