fix[devtools]: gracefully handle missing nodes in TREE_OPERATION_REMOVE instead of crashing

[MD-Mushfiqur123]

Summary

When React re-renders components quickly (e.g., during scrolling or rapid state updates), DevTools tree operations can arrive out of order. This causes TREE_OPERATION_REMOVE to either:

• Try removing a node that was already removed in a previous operation
• Try removing a node from a parent that was already removed

The previous code called this._throwAndEmitError() which crashes the entire DevTools extension and shows an error overlay. This fix gracefully handles these race conditions by logging a warning (debug builds only) and skipping to the next operation.

Changes

In packages/react-devtools-shared/src/devtools/store.js:

Before	After
_throwAndEmitError(Error(...)) + break	if (__DEBUG__) { console.warn(...) } + continue
🚫 Crashes DevTools on race condition	✅ Gracefully skips already-removed nodes

Key design decisions:

• continue instead of break: If one node in a batch is already gone, we should still process the rest of the batch
• __DEBUG__ guard: Warnings only in debug builds; production silently handles the race condition
• Legitimate errors preserved: The "Node was removed before its children" error still correctly throws (that's a real logic bug, not a race condition)

Related Issues

Fixes #33738, #25884

Test Plan

• Manual code review — changes are minimal and targeted
• Existing Store tests should pass (note: requires full React build setup)

[meta-cla]

Hi @MD-Mushfiqur123!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!