Book 7 · Lesson 7.11 · deep-dive

Deep-dive — React 19 features at work

  • Place React 19 runtime features in browser pipeline context
  • Contrast work-repo React with SolidJS radar runtime
  • Avoid reshaping millipede frontend for novelty

Prerequisites: 0.6 · 7.A2

Appendix 7.A3 — React 19 at work vs the browser runtime Team Radar uses.

Download HTML/JSVite serves SolidJS bundle to the browser

React 19 (work context)

  • Actions — async transitions with pending UI states
  • use() — read promises/context in render
  • Document metadata — head tags from components

These solve React app ergonomics — not a reason to swap SolidJS on radar.

Same runtime, different library

Both run in the pipeline above: fetch → parse → JS → paint. Solid signals and React hooks are library choices atop the same browser.

Pattern judgment

Adopt React 19 patterns in maverick-ui where the team ships React. Teach event-driven design in millipede with the PDF stack.

Teach-back prompt

Name one React 19 feature you would demo at work but would not port to radar — and why.