webpack HMR Client
Forgot the /schemas
directory.
host: { client: '*' }
to instruct client WebSockets
to connect to window.location.hostname
.validTargets
option to allow setting other valid build targets aside from 'web'
.port
is now 0
, meaning a dynamic, system-assigned port will be used by default. In most cases there is no need to specify a port for the WebSocket
server.hot
option to hmr
as 'hmr' is more semantically correct, and 'hot' is too vague.WHC_TARGET
environment variable now does nothing. Use the validTargets
option.See the README for a revised list of Gotchas
Possible breaking change in how the client entry script is added to entries. As of v3.0.0 only the first entry in a compiler config will have the client entry script appended to it. That could have been considered a fix, but would produce a breaking change for anyone that was relying on that bug being in place.
In environments which serve multiple bundles to the same page from a single config, webpack-hot-client
will now only allow once instance of the client entry script to run, creating only one WebSocket
, which is all that is needed. That could have been considered a fix, but would produce a breaking change for anyone that was relying on that bug being in place.