Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions .changeset/autoconnect-query-parsing.md

This file was deleted.

13 changes: 0 additions & 13 deletions .changeset/client-disconnect-feedback.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/client-embedded-query.md

This file was deleted.

11 changes: 0 additions & 11 deletions .changeset/client-error-action.md

This file was deleted.

16 changes: 0 additions & 16 deletions .changeset/client-in-a-worker.md

This file was deleted.

23 changes: 0 additions & 23 deletions .changeset/client-live-reload.md

This file was deleted.

15 changes: 0 additions & 15 deletions .changeset/client-logger-name.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/client-logger-without-webpack.md

This file was deleted.

45 changes: 0 additions & 45 deletions .changeset/client-options-both-ways.md

This file was deleted.

7 changes: 7 additions & 0 deletions .changeset/client-packaging.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
"webpack-dev-middleware": patch
---

pr: #2428

The client exports ship type declarations and are marked as the ES modules they are. The client logs through webpack's `Logger` without `webpack/lib/logging/runtime.js`, so `universal` and `["web", "node"]` bundles no longer pull in a node builtin and a page enforcing Trusted Types needs no guard. A module that re-exports the client can hand it its options through `__webpack_dev_middleware_client_query__`, and `?autoConnect` is read like every other boolean.
7 changes: 7 additions & 0 deletions .changeset/client-page-feedback.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
---
"webpack-dev-middleware": minor
---

pr: #2425

The client posts build events to the page the way webpack-dev-server's does (`webpackOk`, `webpackErrors`, `webpackClose` and the rest), logs `Disconnected!` when the connection drops and clears the build's problems from the overlay until it is back. `progress` accepts `"circular"` or `"linear"`. Reloads skip a page that is already navigating away, use the nearest ancestor with a url of its own inside an `about:blank` iframe, and in `apply: "reload"` follow a sibling compilation's build too.
19 changes: 0 additions & 19 deletions .changeset/client-path-in-parts.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/client-postmessage-and-reload-guards.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/client-reload-on-sibling-builds.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/client-retries-infinity.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/client-transports.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/client-type-declarations.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/client-url-hot-overrides.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/connect-object-from-node.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/connected-log-both-transports.md

This file was deleted.

4 changes: 3 additions & 1 deletion .changeset/deprecate-hot-progress.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,6 @@
"webpack-dev-middleware": patch
---

Deprecated the `hot.progress` option; it will be removed in the next major release and keeps working until then. It applied `ProgressPlugin` to your compiler, which leaves a server that applies one itself — webpack-dev-server does — with two of them on one compiler. Apply it yourself and hand the result to [`publish`](https://github.com/webpack/webpack-dev-middleware#publishpayload), rounding the percent and dropping a tick that repeats one as the option did for you. The browser end of this, `hot.client.progress`, is unaffected and stays.
pr: #2451

Deprecated `hot.progress`, which keeps working until the next major release: a server that applies `ProgressPlugin` itself ended up with two on one compiler. Remove it, apply the plugin yourself and hand its ticks to [`publish`](https://github.com/webpack/webpack-dev-middleware#publishpayload); the browser-side `hot.client.progress` is unaffected.
33 changes: 0 additions & 33 deletions .changeset/feat-problem-formatter.md

This file was deleted.

19 changes: 0 additions & 19 deletions .changeset/fix-empty-overlay-and-stuck-indicator.md

This file was deleted.

20 changes: 0 additions & 20 deletions .changeset/fix-overlay-file-references.md

This file was deleted.

Loading
Loading