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 the undocumented option filename isn't set, it will attempt to match /Users/tom/Documents/somewebsite/dist/undefined, fail, and the request will fall through to the next handler, regardless of the file.
Setting { lazy: true, filename: "client.js" } in the dev-middleware config allows it to handle the request, but this won't work for webpack configurations with multiple entry points.
The text was updated successfully, but these errors were encountered:
grrowl
changed the title
lazy: true won't ever trigger rebuild without undocumented option set.lazy: true won't ever trigger rebuild without undocumented option "filename" set.
Feb 5, 2015
It's also worth mentioning in the readme that lazy compilation is incompatible with Hot Module Replacement (although in hindsight, it should have been moderately obvious)
Closing this very old issue, since it appears to have been fixed a while ago. filename is now a documented option, and this middleware also works if you don't define it.
I have it narrowed down to line 135 of middleware.js:
When the undocumented option
filename
isn't set, it will attempt to match/Users/tom/Documents/somewebsite/dist/undefined
, fail, and the request will fall through to the next handler, regardless of the file.Setting
{ lazy: true, filename: "client.js" }
in the dev-middleware config allows it to handle the request, but this won't work for webpack configurations with multiple entry points.The text was updated successfully, but these errors were encountered: