React Scan prevents React DevTools from working

[phou-figma]

React Scan seems to interfere with React DevTools, making it unusable when both extensions are enabled:

Versions:

• React DevTools - 6.1.5 (7/4/2025)
• React Scan - 1.0.9
• Chrome - Version 138.0.7204.184 (Official Build) (arm64)

[h3adache]

This is still broken even when using the zip from https://github.com/aidenybai/react-scan/blob/main/BROWSER_EXTENSION_GUIDE.md#chrome that includes version 1.1.4

[txbm]

Came here looking for this exact issue, can confirm broken on Chrome 139, React 19, React Scan 0.3.2

[lehovec]

Same problem, I found temporary fix by load it asynchronously:

  setTimeout(async () => {
    const { scan } = await import("react-scan");
    scan({
      enabled: true,
      trackUnnecessaryRenders: true,
    });
  }, 1000);

[aaditmshah-commversion]

I can't view the React DevTools component tree when using React Scan. Loading React Scan asynchronously didn't help either. This is a major issue that needs to be fixed.

[joeyfigaro]

Since react-scan hacks React's internals, I had just assumed it was a one tool or the other kind of deal. @aaditmshah-commversion @txbm

They're using bippy to setup react-scan, so.

[txbm]

@joeyfigaro yeah we ended up reaching the same conclusion and just dropped react-scan entirely in favor of just using browser native repaint/FPS profiling tools. Ultimately the component render flashing thing seemed like it would be useful but in practice wasn't that much more useful than just looking at composite layer repaints + total FPS and then call stacks to figure out what component was misbehaving

[elvismdev]

Same here, it totally disabled the React DevTools for me when I installed the React Scan chrome extension. Also while at it and testing it out, it failed to identify others components that are unnecessarily re-rendering, which React DevTools Profiler properly identifies and flags.