Results 76 comments of Rob Pruzan

Yeah we have a fallback for usage without workers. We can add an option for scan({...}) to control this explicitly

> Maybe, but my next.js app where it repros is a large complex 6 year old app so it'll be very hard to replicate! Are you using react scan in...

> I'm not sure. I just installed the Chrome extension from https://github.com/aidenybai/react-scan/blob/main/BROWSER_EXTENSION_GUIDE.md and ran it in my localhost dev server. > > React Scan 1.0.8 Sorry let me clarify, in...

Yep looking into best options for this

This is a mistake and is a deprecated API that was accidentally not fully removed. We may add this back, will have to think a little about it. What this...

This error is no longer present in [email protected] If you want to run react-scan in production you can use the following: ``` import {scan} from 'react-scan/all-environments' scan() //

Thanks for the report. For anyone with similar issues, the bug is because we incorrectly derive the component tree. If a component does not render "host components", aka components with...

Are you using our build plugin (react-component-name)? This provides component names even when using something like a minifier/react compiler, but only for components defined in your project (one's in node_modules...