CodeVetter · Repo Unpack · Behavior traces
facebook/react
Three flows are worth walking: (1) client startup/first paint, from `createRoot` through the microtask scheduler into render and commit; (2) the compile flow, where Babel hands a function to either the TS `Pipeline.ts` or the Rust `pipeline.rs`; (3) the release flow, where a commit becomes npm artifacts. The commit phase in particular is a fixed three-pass sequence with `root.current = finishedWork` as the atomic swap point between mutation and layout, and passive effects flushed later. Each trace below names the functions in call order with line anchors.
- Startup trace: `createRoot(container, options)` → validate via `isValidContainer` → `createContainer(container, ConcurrentRoot, …, onUncaughtError, onCaughtError, onRecoverableError)` → `markContainerAsRoot(root.current, container)` → `listenToAllSupportedEvents(rootContainerElement)` → `new ReactDOMRoot(root)`.
- First render trace: `root.render(children)` → `updateContainer` → `updateContainerImpl` → `requestUpdateLane(current)` → `createUpdate(lane)` → `enqueueUpdate(rootFiber, update, lane)` → `scheduleUpdateOnFiber(root, rootFiber, lane)`.
- Scheduling trace: `scheduleUpdateOnFiber` → `markRootUpdated(root, lane)` → `ensureRootIsScheduled(root)` → `ensureScheduleIsScheduled()` → `scheduleImmediateRootScheduleTask()` → (microtask) `processRootScheduleInMicrotask` → `scheduleTaskForRootDuringMicrotask` → `Scheduler_scheduleCallback(priorityLevel, performWorkOnRootViaSchedulerTask)`.
- Render trace: `performWorkOnRoot(root, lanes, forceSync)` computes `shouldTimeSlice`, dispatches to `renderRootConcurrent` (line 2779) or `renderRootSync` (line 2623), then loops on the `RootExitStatus` — handling `RootInProgress` (yield, `startYieldTimer`), store inconsistency (re-render sync), and `RootErrored` (`getLanesToRetrySynchronouslyOnError` → `recoverFromConcurrentError`).
- Component render trace: for each function component the reconciler calls `renderWithHooks`, which installs the mount-or-update dispatcher on `ReactSharedInternals.H`, invokes the component, then restores `ContextOnlyDispatcher`; `bailoutHooks` is the memoized fast path.
- Commit trace: `commitRoot` (line 3725) → `commitBeforeMutationEffects(root, finishedWork, lanes)` → `commitMutationEffects(root, finishedWork, lanes)` → `root.current = finishedWork` (the tree swap, line 4051) → `commitLayoutEffects(finishedWork, root, lanes)` → `flushSpawnedWork()`; passive effects run later via `flushPendingEffects` → `commitPassiveMountEffects`.
- Yield trace: inside a Scheduler task, `workLoop(initialTime)` drains the min-heap and stops when `shouldYieldToHost()` returns true (elapsed ≥ `frameInterval`); the continuation is re-armed by `schedulePerformWorkUntilDeadline()` through `setImmediate`/`MessageChannel`/`setTimeout`.
- SSR trace: `renderToPipeableStream(children, options)` → `createRequestImpl` → `createRequest(...)` → `startWork(request)` (line 6370) → tasks retried through `retryTask`/`renderNode` → consumer calls `pipe(destination)` → `startFlowing(request, destination)` (line 6464) → `flushCompletedQueues` (line 6175); `abort(request, reason)` is the cancellation path (line 6557).
- Server Action trace: HTTP POST FormData → `decodeAction(body, serverManifest)` → detect `$ACTION_REF_*` or `$ACTION_ID_*` → `decodeBoundActionMetaData` (for bound args) → `loadServerReference` → `resolveServerReference(bundlerConfig, id)` → `preloadModule` → `requireModule` → `bindArgs(fn, args)` → returned action `fn.bind(null, formData)`.
- TS compile trace: `compileFn` builds `Environment` from `findContextIdentifiers(func)`, then runs `lower(func, env)` → `PruneMaybeThrows` → `ValidateContextVariableLValues` → `MergeConsecutiveBlocks` → `SSA` → `EliminateRedundantPhi` → `ConstantPropagation` → `InferTypes` → `AnalyseFunctions` → `InferMutationAliasingEffects` → `DeadCodeElimination` → `InferMutationAliasingRanges` → `InferReactivePlaces` → `buildReactiveFunction` → `renameVariables`, logging each step through the `log(value)` callback.
- Rust compile trace mirrors it: `compile_fn` → `react_compiler_lowering::lower` → `validate_context_variable_lvalues` → `validate_use_memo` → `enter_ssa` → `eliminate_redundant_phi` → `infer_types` → `analyse_functions` → `infer_mutation_aliasing_effects` → `infer_mutation_aliasing_ranges` → validations → `infer_reactive_places` → `infer_reactive_scope_variables` → scope alignment passes.
- The compiler is fault-tolerant rather than fail-fast: passes call `env.recordError(diagnostic)`, validation passes are wrapped in `env.tryRecord(() => pass(hir))`, and errors are aggregated at the end via `env.hasErrors()` / `env.aggregateErrors()` — `CompilerError.invariant()` is the only category that always throws.
- Rust bailout trace: `prefilter.ts` walks the Babel AST first and only forwards functions that are component/hook declarations or carry an opt-in directive, so the napi boundary is never crossed for ordinary functions.
- Release trace: `yarn build` → `prebuild` links the compiler via `scripts/react-compiler/link-compiler.sh` → `build-all-release-channels.js` → `buildForChannel(channel)` spawns `scripts/rollup/build.js` → `processStable`/`processExperimental` rewrite versions from `ReactVersions.js` + short SHA → `scripts/release/publish.js` validates tags and publishes with OIDC.
- Error-minification trace: prod bundles emit `/*! <expected-error-format>"…"</expected-error-format>` markers; `yarn extract-errors` greps the `build` dir with `execSync('git --no-pager grep …')`, assigns the next free numeric code, and appends to `scripts/error-codes/codes.json` (~66 KB of registered messages).