-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome extension makes sites with production build unresponsive #219
Comments
I need to say that I face this too, I recently download the extension and find many React websites too slow and crashing. I just remove the extension and things back to work fine. |
I don't really maintain this project anymore. Unfortunately I was never able to get it to only run when the dev tools are opened. I suggest installing extension into its own chrome user profile. |
I just want to confirm this is also the case if React DevTools and React-Sight are both used while accessing Asana. |
Could you please state the fact that this is currently unmaintained and that it will break websites that use React in production in some prominent places (like the add-ons pages for Firefox, Chrome and the Github repo)? You will spare many people hours of trying to figure out, why some specific websites stopped working for them. Especially since there can be a delay between installing the add-on and having the first site break, if you use it only for development at first. |
I'm getting the same error, React site get unresponsive, Chrome Version: 87.0.4280.88 (Official Build) (x86_64) React version: ^16.13.1 |
Overview
When the extension is enable on Chrome and one navigates to a web page that is using the production build of React, the page becomes unresponsive and/or slow.
How to reproduce
If you go to react i18next documentation page, while the extension is enabled, then try to navigate to a section using the side bar, the page hangs up.
Testing notes
I've tested this by using the incognito tab, then enabling one extension at a time till the issue presented itself.
Versions
The text was updated successfully, but these errors were encountered: