-
Notifications
You must be signed in to change notification settings - Fork 2
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
Ability to disable react-error-overlay #11
Comments
The root issue might be that all fixtures are bundled together, so if you have a compile error in one of your fixtures webpack can't bundle any fixtures. |
It's bundling them, but |
Can you post a screenshot of the error overlay? I'm curious if it's a compilation error, a module runtime error or a render runtime error. If it's the 1) webpack can't bundle. If it's 3) it only appears on the component that crashes, the rest should load just fine. Maybe it's 2). Or maybe it's some linting/optional errors that I'm not familiar with. |
It's probably this. IIRC it was some type checking errors. I don't have a screenshot in this case. |
While refactoring many files one may create compile warnings across multiple files. Because
react-error-overlay
doesn't let you see the component/fixture you're working on until there are no errors, you can't easily iterate through files one at a time. You have to go fix all the compile errors before viewing the component you're currently working on.You can inspect the overlay and delete it from the DOM showing the component/fixture you're working on.
The text was updated successfully, but these errors were encountered: