build: update dependency webpack-dev-middleware to v8 (main)

[angular-robot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
webpack-dev-middleware	7.4.5 → 8.0.0

---

• If you want to rebase/retry this PR, check this box

---

Release Notes

webpack/webpack-dev-middleware (webpack-dev-middleware)

v8.0.0

Compare Source

Major Changes

• The getFilenameFromUrl function is now asynchronous, returning a Promise that resolves to the object with the found filename (or undefined if the file was not found) or throws an error if the URL cannot be processed. Additionally, the object contains the extra property with stats (file system stats) and outputFileSystem (output file system where file was found) properties. (by @​alexander-akait in #​2284)

• Minimum supported Node.js version is 20.9.0. (by @​alexander-akait in #​2284)

• Minimum supported webpack version is 5.101.0. (by @​alexander-akait in #​2284)

Minor Changes

• Added support for plugin usage, useful when the middleware will be used as a webpack plugin (no stats output, no extra actions). (by @​alexander-akait in #​2284)

• Added the forwardError option to enable error forwarding to next middleware. (by @​alexander-akait in #​2284)

• Enable cacheImmutable by default for immutable assets. (by @​alexander-akait in #​2284)

Patch Changes

• Improved initial loading module time. (by @​alexander-akait in #​2284)

• Removed outdated code and improved performance by avoiding extra loops. (by @​alexander-akait in #​2284)

All notable changes to this project will be documented in this file. See standard-version for commit guidelines.

7.4.5 (2025-09-24)

Bug Fixes

• unpin memfs (#​2176) (c9a0e68)

7.4.4 (2025-09-23)

Bug Fixes

• pin memfs version (#​2174) (044d691)

7.4.3 (2025-09-05)

Bug Fixes

• do not call the next middleware for 304 responses (#​2155) (c26a326)
• do not call the next middleware when request is finished or errored (#​2156) (116c680)

7.4.2 (2024-08-21)

Bug Fixes

• no crash when headers are already sent (#​1929) (c20f1d9)

7.4.1 (2024-08-20)

Bug Fixes

• assetsInfo may be undefined (rspack) (#​1927) (21f1797)

[gemini-code-assist]

Code Review

This pull request updates webpack-dev-middleware to version 8.0.0, which is a major update containing breaking changes. A significant breaking change makes this update incompatible with webpack-dev-server@5.2.3, which is a dependency in this project. This creates a risky situation and should be addressed. I have left a comment detailing the issue.

[gemini-code-assist]

This update to webpack-dev-middleware v8.0.0 creates a serious mismatch between compile-time types and runtime behavior.

@angular-devkit/build_angular has a direct dependency on webpack-dev-middleware, which appears to be for resolving TypeScript types. With this change, it will resolve to v8.0.0.

However, webpack-dev-server@5.2.3, which is used at runtime, depends on webpack-dev-middleware@^7.0.0. pnpm will correctly provide webpack-dev-server with a v7 release of the middleware, avoiding an immediate runtime crash. This creates a dangerous situation where the code is compiled against v8 types, but runs against a v7 implementation. While this might not break immediately if the used options are compatible, it is a fragile setup.

A key breaking change in webpack-dev-middleware@8.0.0 is that getFilenameFromUrl is now async. webpack-dev-server@5.2.3 uses it synchronously. If for any reason webpack-dev-server resolves to v8 at runtime, it will break.

To avoid this fragility and potential for runtime errors, this dependency should be kept in sync with what webpack-dev-server supports. This update should be reverted until webpack-dev-server officially supports webpack-dev-middleware v8.

Suggested change

	"webpack-dev-middleware": "8.0.0",
	"webpack-dev-middleware": "7.4.5",