
We should probably catch and silence all exceptions from the devtools (when not in dev mode) and have reasonable fallback behavior.
@spicyj moving these errors to warnings (with console.warn) is ok?
Yeah, catching them and displaying them as warnings would be okay – would be best to clearly prefix the warning message to indicate that it is an issue with react-devtools.
@spicyj do you think we should to setup something like Sentry to log these errors from the users? 💃
I think they'll file issues instead. I doubt using Sentry in the devtools would go over well with privacy-conscious folks.
Not sure if this is the right place to comment, but when devtools extension is enabled I get a security error: Your connection to this origin is not secure.
This is caused by the build/backend.js file in React Dev Tools.
React DevTools has been rewritten and recently launched a new version 4 UI. The source code for this rewrite was done in a separate repository and now lives in the main React repo (github.com/facebook/react).
Because version 4 was a total rewrite, and all issues in this repository are related to the old version 3 of the extension, I am closing all issues in this repository. If you can still reproduce this issue, or believe this feature request is still relevant, please open a new issue in the React repo: https://github.com/facebook/react/issues/new?labels=Component:%20Developer%20Tools
Most helpful comment
I think they'll file issues instead. I doubt using Sentry in the devtools would go over well with privacy-conscious folks.