react

React DevTools Store walks operations array and can throw an uncaught error: This desync occurs when elements are filtered or unmounted, but a reorder operation for their children is still processed. Throwing an uncaught error in the bridge listener crashes the entire DevTools extension panel, rendering it unusable. This change modifies and cases in to gracefully skip the reordering operation (by advancing the pointer past the child IDs) instead of throwing an error. How did you test this change? Verified that it does not crash when receiving operations for missing/filtered nodes in desynced states. Ran DevTools Jest test suite:

Fixes #37264 Context & Problem During active React DevTools Profiler sessions, when components unmounted mid-recording, the profiler retained stale commit timestamps for unmounted Fiber nodes. This resulted in cumulative timing distortions in the Profiler flame chart and ranked charts, displaying inflated render durations for components that were no longer mounted. Solution & Changes Updated component unmount event handling in to recalculate and finalize active profiling session durations at unmount time. Ensures unmounted Fibers clear their transient duration state so subsequent commits accurately measure active components only. Testing & Verification Verified flame chart and ranked chart render times when components unmount dynamically during an active profiling recording.

Fixes #37261 Context & Problem When React DevTools inspects custom hook chains on complex components, the hook name parser walks the JavaScript AST to resolve named functions and custom hook calls. In components utilizing conditional hook patterns or transpiled code with sparse AST nodes, encountering a or unhandled AST node caused DevTools to throw an unhandled during hook inspection, preventing component trees from rendering in the DevTools panel. Solution & Changes Added explicit and guards to AST node traversal loops in . Implemented fallback safety bounds during AST node parent traversal so unhandled node types safely return fallback names without breaking tree inspection. Testing & Verification Verified hook name resolution against custom hook chains containing conditional expressions, optional chaining, and null AST nodes.