-
Notifications
You must be signed in to change notification settings - Fork 194
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
Is there a way to disable this plugin on a specific entry? #428
Comments
If they both run in the same Webpack instance there are no safe way to disable it because the runtime is injected globally and any HMR to any entry would propagete. |
I have a similar issue where my browser extension has a full-page mode and also injects code into websites. Notably, there are two issues when code is injected into websites:
I think point (2) should be addressable similar to what was done in #146 (do not inject the overlay for excluded entries). I tried to use the existing |
Hey, sorry I totally missed this comment. In short, currently this is impossible due to how error overlays work: we listen on the global error and unhandled rejection events. React (nor do Webpack) does not expose "where" some error is originated, so it is complicated to filter out errors from "excluded" entries. In theory this could work, but would be very unreliable when things are transpired, mini died or uglified. |
@pmmmwh Any news about it? Thanks! |
@pmmmwh im also interested in this feature. I split some analytics code and when i have two webpack entries i get weird errors when updating a component which is just in the main app. For example
while with a single entry i do not have this. So if i could exclude one that would help. I didnt look that much deeper into why this is hapening. |
I have mutiple entries, such as pageA and pageB. They render in different html. So I don't want to pageB get refresh when I was edit components used in pageA.
The text was updated successfully, but these errors were encountered: