v4.1.1

Bugfixes

• fix: fixes #86, client port bungle #87

v4.1.0

Updates

• https better server support (#85)

Features

• client-server port config (#85)

v4.0.3

Bugfixes

• fix: incorrect check for existing socket clients (#77)
• fix: prevent validation errors if no options passed (#75)

v4.0.2

Bugfixes

• fix: webpack-defaults to devDeps

Updates

• docs: fix missing url references from defaults upgrade

v4.0.1

Forgot the /schemas directory.

v4.0.0

Bugfixes

• fix: throw error when HMR plugin exists in config (#66)
• fix: hotClientOptions when autoConfigure: false (#65)

Features

• feat: allEntries applies client entry to all entries (#64)
• Added the ability to pass host: { client: '*' } to instruct client WebSockets to connect to window.location.hostname.
• Added the validTargets option to allow setting other valid build targets aside from 'web'.

Updates

• Added documentation for Remote Machine Testing options.
• Moved documentation for Communicating with Client WebSockets

Breaking Changes

• The default 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.
• Changed the hot option to hmr as 'hmr' is more semantically correct, and 'hot' is too vague.
• The WHC_TARGET environment variable now does nothing. Use the validTargets option.

See the README for a revised list of Gotchas

v3.0.0

Bugfixes

• fix: multiple entries, add autoConfigure option (#58)
• fix: duplicate logging in MultiCompilers. fixes #47 (#59)
• fix: strip ansi from warnings, errors. fixes #46 (#57)

Features

• feat: granular control of client warnings, errors. fixes #55 (#56)

Breaking Changes

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.

v2.2.2

Bugfixes

• Fix missing options argument in check call (#45)

v2.2.1

Bugfixes

• Add slashes to socketUrl for IE11/Edge. (#43)

v2.2.0

Features

• add envar to allow build target override (#38)
• add ability to broadcast to client sockets (#39)

Updates

Webpack 3 code is now removed. This should have been done in 2.0.0 but it was missed. This shouldn't impact users as 2.0.0 officially dropped support in peerDeps for webpack@3.