You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it works with multiple entry points. The main assumptions to me that would fail in any projects not from CRA would be the custom dev server middlewares and cheap-module-source-map (devtool). It also won't work with resource queries, custom socket implementations nor webpack under proxy servers, but I would consider them as advanced use cases anyhow, and thus will definitely need custom work.
then I'm now using offical webpack-dev-server, with no custom socket implementations, no proxy and using cheap-module-source-map but overlayer still not work
what need to support overlayer? or It only work in CRA project?
Update:
I found that it's because I shoud not expect warning to cause error overlayer after debug。 but there is still a problem
If I turn off webpack-dev-server's overlay, how to display overlayer for warning. because this plugin only display overlayer when error
If I turn on webpack-dev-server's overlay, It will appear two overlayer for errors.
I wonder if the overlay of this plugin is just a replacement of webpack-dev-server, and can we have a options to turn it off and only use webpack-dev-server's built-in overlayer?
The text was updated successfully, but these errors were encountered:
githoniel
changed the title
error overlayer no work
error overlayer not work
Jan 6, 2020
githoniel
changed the title
error overlayer not work
error overlayer not work when warning
Jan 6, 2020
building error only result in console warning but no error overlayer
I notice in #1 (comment)
then I'm now using offical webpack-dev-server, with no custom socket implementations, no proxy and using
cheap-module-source-map
but overlayer still not workwhat need to support overlayer? or It only work in CRA project?
Update:
I found that it's because I shoud not expect warning to cause error overlayer after debug。 but there is still a problem
I wonder if the overlay of this plugin is just a replacement of webpack-dev-server, and can we have a options to turn it off and only use webpack-dev-server's built-in overlayer?
The text was updated successfully, but these errors were encountered: