-
Notifications
You must be signed in to change notification settings - Fork 296
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
Handle when unacceptedModule
is not in moduleMap
#306
Comments
This is a good idea, i’d take a pull request for it. The other option might be to remove this feature entirely and advise people to use the named modules plugin |
I encountered a similar issue but in my case moduleMap didn't contain renewedModules which resulted in a bunch of - undefined in the console. Is there a known solution for that?
"./src/scripts/apps/enb/app.js" "./src/scripts/apps/enb/routes/index.js" "./src/scripts/apps/enb/routes/records.js" Is it possible that because of the code splitting the module map doesn't have any information about its parent modules and hence it prints out undefined? Would it be possible in this case to print out renewedModule id as a fallback? |
Yep, that seems sensible, i’d take a PR. |
I encountered a problem where the module that could not be updated was not in the
moduleMap
resulting in- undefined
being printed when listing the modules that couldn't be hot updated.webpack-hot-middleware/process-update.js
Lines 88 to 108 in 78c9e7e
The text was updated successfully, but these errors were encountered: