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
When using this plugin to create separate dll for vendor libs I find out that certain type of files or even code paths break webpack HMR, it starts infinitely rebuilding and log notifications into console log, so my console window became spammed very quickly. First it happens when I add an image and just serve it as in html. For some reason this plugin didn't like my image, ok I've changed to another then spam finished. But next time when I add nested lazy routes into my app it breaks HMR again, this time I have no choice just switch HMR off which is very sadly. It works with 1 level of lazy routes, but as soon as you add nested it breaks immediately (infinite rebuilding). When I remove DllBundlePlugin out of dev config problems gone, but then I get huge main.js...
Could this be fixed? Or maybe somebody know some workaround?
The text was updated successfully, but these errors were encountered:
I am having the same issue and still waiting for help. Somebody says turning off the HotModuleReplacement might be helpful and you could have a try. It didn't work for me though.
When using this plugin to create separate dll for vendor libs I find out that certain type of files or even code paths break webpack HMR, it starts infinitely rebuilding and log notifications into console log, so my console window became spammed very quickly. First it happens when I add an image and just serve it as in html. For some reason this plugin didn't like my image, ok I've changed to another then spam finished. But next time when I add nested lazy routes into my app it breaks HMR again, this time I have no choice just switch HMR off which is very sadly. It works with 1 level of lazy routes, but as soon as you add nested it breaks immediately (infinite rebuilding). When I remove DllBundlePlugin out of dev config problems gone, but then I get huge main.js...
Could this be fixed? Or maybe somebody know some workaround?
The text was updated successfully, but these errors were encountered: