OSS Feed: 2026-03-28

A busy Friday across the React and Next.js ecosystem. Andrew Clark shipped a React fix and experimented with offline hooks in Next.js, Tanner Linsley dropped a major RFC for TanStack DB, and Theo pushed forward on t3code. Here's the full rundown.

@acdlite

Active day for Andrew. He landed a fix in React core and opened two experimental drafts in Next.js:

• Fix context propagation into Suspense fallbacks — facebook/react#36160 — Addresses a bug where context values weren't properly propagating into Suspense fallback boundaries.
• [experiment] Add useOffline hook to expose offline state to userland — vercel/next.js#92012 (draft) — A new hook that lets components react to offline/online state transitions.
• [experiment] Add useOffline flag with offline retry behavior — vercel/next.js#92011 (draft) — Companion PR adding automatic retry logic when connectivity is restored.

@gaearon

Dan was active in the React docs and Next.js issue trackers:

• Commented on the Italian translation progress for React docs — reactjs/it.react.dev#418
• Weighed in on the TS71007 serializable props warning not working with export default — vercel/next.js#55332
• Reviewed proposals for next/image as MDX component — reactjs/react.dev#4382
• Commented on getDerivedState docs for createClass — reactjs/react.dev#1214

@tannerlinsley

Tanner dropped a significant RFC:

• RFC: DbClient — Dependency Injection, Stateless Collection Descriptors, and SSR Hydration — TanStack/db#1420 — A design proposal for TanStack DB covering DI patterns, stateless collection descriptors, and SSR hydration strategies. This could shape the future architecture of TanStack DB significantly.

@timneutkens

Tim reviewed PRs in the Next.js repo:

• Commented on fix: preserve Request body source in patch-fetch — vercel/next.js#90886
• Commented on chore(build): replace deprecated critters package with beasties — vercel/next.js#88640

@bvaughn

Brian participated in React docs discussions:

• Commented on Document how React treats different attributes — reactjs/react.dev#80 — A long-standing issue about clarifying React's attribute handling behavior.

@t3dotgg

Theo pushed two PRs to t3code:

• Add browser-based session auth bootstrap — pingdotgg/t3code#1458 (draft) — Adding browser-based authentication flow to t3code.
• Add keyboard shortcuts for jumping to sidebar threads — pingdotgg/t3code#1456 — Quality-of-life improvement for navigating threads via keyboard.

@TkDodo

Dominik was busy across Sentry and TanStack Query:

• Reviewed several Sentry refactoring PRs: OwnerInput class-to-function conversion (#110200), select field types improvement (#110454), nav tour context split (#110341), tour rename (#110387), and issue detail margin fix (#110479)
• Reviewed feat(vue-query): Add mutationOptions — TanStack/query#10036 — Adding mutationOptions helper to the Vue Query adapter.

@phryneas

Lenz was active in the Apollo Client ecosystem:

• Commented on useSuspenseQuery data nullish issue — apollo-client-integrations#527 — Addressing a discrepancy between docs and runtime behavior for Suspense query data.
• Commented on Expose Apollo Client instance in loader handler — apollo-client-integrations#543

@kettanaito

Artem was active across MSW and related tooling:

• Commented on feat: implement msw plugin for openapi-ts — hey-api/openapi-ts#3570 — MSW handler generation from OpenAPI specs.
• Commented on Update path-to-regexp to >= 8.4.0 — mswjs/msw#2686
• Commented on MSW stops handling requests after 5 mins in page hidden state — mswjs/msw#2635 — A tricky browser lifecycle issue affecting service worker reliability.

Quiet Day

• @sebmarkbage — No public activity
• @leerob — No public activity
• @markerikson — No public activity

---

Today's Highlight

Tanner Linsley's TanStack DB RFC (TanStack/db#1420) stands out today. The proposal tackles three fundamental challenges at once — dependency injection for testability, stateless collection descriptors for cleaner APIs, and SSR hydration for framework compatibility. If you're following the TanStack ecosystem, this RFC is worth reading and commenting on.

Also notable: acdlite's useOffline experiments in Next.js hint at first-party offline support coming to the framework, which would be a significant step for PWA-style Next.js apps.