andras/decla-red
andras/decla-red
Watch
1
0
Fork
You've already forked decla-red
 0
Code Issues Pull requests 8 Projects Releases Packages 1 Wiki Activity Actions

Update dependency webpack-dev-server to v6 #24

Open
andras wants to merge 1 commit from renovate/webpack-dev-server-6.x into main
pull from: renovate/webpack-dev-server-6.x
merge into: andras:main
Conversation 1 Commits 1 Files changed 1 +1 -1
andras commented 2026-10-31 06:10:21 +00:00
Owner

This PR contains the following updates:

Package Type Update Change
webpack-dev-server devDependencies major ^5.2.4 → ^6.0.0

Release Notes

webpack/webpack-dev-server (webpack-dev-server)

v6.1.0

Compare Source

Minor Changes

  • Run as a plugin from the top-level plugins of a multi-configuration, serving every configuration from one server. (by @​alexander-akait in #​5765)

  • Fix client progress modes, socket URL credentials, overlay and progress lifecycles, server startup error handling and local IP lookup; export BaseServer. (by @​alexander-akait in #​5739)

  • The browser client, the error overlay and both transports now come from webpack-dev-middleware, so this package has no client code of its own. Every option keeps its name and meaning, allowedHosts and the origin checks still apply here, and this server's { type } messages are still sent next to the middleware's, so React Refresh keeps working. client/index.js, client/socket.js and client/clients/WebSocketClient.js still resolve while the client's internal files are gone, and the console wording, the overlay and the progress indicator are now the middleware's. client.webSocketTransport: "sse" adds Server-Sent Events, a universal build now runs in Node without the client throwing, and sendMessage(), getClientEntry() and getClientHotEntry() still work, a subclass's overrides included, but are deprecated. (by @​alexander-akait in #​5750)

Patch Changes

  • Keep hot and live reload working after a cancelled "Leave site?" dialog. (by @​alexander-akait in #​5744)

  • Keep the overlay for a runtime error thrown while the page is still loading. (by @​alexander-akait in #​5745)

  • Validate the Host and Origin headers and enforce same-origin checks on WebSocket upgrade requests handled by proxies with ws: true. This prevents cross-origin pages from connecting to proxied WebSocket services through the development server. (by @​UlisesGascon in cb1534a)

  • Validate options with a precompiled schema to cut ~115ms from startup. (by @​alexander-akait in #​5746)

  • Validate Host and HTTP/2 authority headers independently of Origin protocol exceptions, including when allowedHosts is "all". Handle malformed open-editor URLs with a controlled response and parse their query without relying on the Host header. (by @​bjohansebas in #​5771)

v6.0.0

Compare Source

Major Changes

  • Bump Express to v5. See the Express 5 migration guide for the full list of breaking changes. (by @​bjohansebas in #​5674)

  • Bump the webpack peer dependency range from ^5.0.0 to ^5.101.0. (by @​bjohansebas in #​5674)

  • Drop support for Node.js < 22.15.0. (by @​bjohansebas in #​5674)

  • Convert the source to native ES modules. The package keeps "type": "module" and now exposes both an ESM and a CommonJS build via the exports field: ESM consumers import the native lib/, while CommonJS consumers require() a transpiled dist/ build — so the package works from both ESM and CommonJS, including environments where require(ESM) is not supported. (by @​bjohansebas in #​5674)

  • Remove CLI flags. Use the serve command from webpack-cli together with a configuration file or the programmatic API instead. (by @​bjohansebas in #​5674)

  • Remove the internalIP and internalIPSync static methods from Server. Resolve the local IP yourself if you need it. (by @​bjohansebas in #​5674)

  • Remove the bypass option from proxy configuration. Use the router or context options provided by http-proxy-middleware instead. (by @​bjohansebas in #​5674)

  • Remove SockJS support. The webSocketServer option no longer accepts "sockjs"; use the default "ws" transport instead. (by @​bjohansebas in #​5674)

  • Remove the spdy dependency. Use the built-in node:http2 module via the server option for HTTP/2 support. (by @​bjohansebas in #​5674)

  • Update http-proxy-middleware to v4. See the http-proxy-middleware v3 release notes and v4 release notes for the full list of breaking changes. (by @​bjohansebas in #​5674)

  • Update webpack-dev-middleware to v8 and sync originalUrl for middleware compatibility. server.middleware.getFilenameFromUrl() is now asynchronous and resolves to { filename, extra: { stats, outputFileSystem } }. See the webpack-dev-middleware v8 release notes for details. (by @​bjohansebas in #​5674)

Minor Changes

  • Add plugin support. webpack-dev-server can now be used as a webpack plugin, integrating with the compiler lifecycle without explicitly passing a compiler, preventing multiple server starts on recompilation, ensuring clean shutdown, and supporting MultiCompiler setups with multiple independent plugin servers. (by @​bjohansebas in #​5674)

  • Enable the compression middleware for HTTP/2 connections. (by @​bjohansebas in #​5674)

  • Remove the colorette dependency in favor of native ANSI styling. (by @​bjohansebas in #​5674)

  • Update chokidar to v5 and extend watchFiles.options.ignored to support glob string patterns via tinyglobby. (by @​bjohansebas in #​5674)

  • Use compiler.platform to determine the target environment instead of inspecting the resolved target string. Universal targets ("universal" or ["web", "node"], where compiler.platform.universal is true since webpack 5.108.0) are treated as web targets so the client runtime is injected. (by @​bjohansebas in #​5674)

  • Use the WHATWG URL API instead of the deprecated url.parse. (by @​bjohansebas in #​5674)

Patch Changes

  • Bump production dependencies, notably open to v11 and p-retry to v8. (by @​bjohansebas in #​5674)

  • Reject cross-site requests to the internal open-editor and invalidate endpoints. They performed state-changing actions (opening a file in the editor, forcing a recompilation) on any GET request, so a page the developer visited could trigger them. They now require a same-origin request, validated via Sec-Fetch-Site with an Origin/Host fallback. (by @​bjohansebas in #​5691)

  • Treat loopback aliases (127.0.0.1, ::1, localhost) as equivalent in isSameOrigin so the WebSocket client does not reject valid same-origin connections. (by @​bjohansebas in #​5674)

  • Migrate the test suite from Jest to node:test and set up the jsdom environment. (by @​bjohansebas in #​5674)

  • Update webpack-cli to v7.0.2. (by @​bjohansebas in #​5674)

v5.2.7

Compare Source

Patch Changes

  • Validate the Host and Origin headers and enforce same-origin checks on WebSocket upgrade requests handled by proxies with ws: true. This prevents cross-origin pages from connecting to proxied WebSocket services through the development server. (by @​github-actions in #​5766)

  • Validate Host and HTTP/2 authority headers independently of Origin protocol exceptions, including when allowedHosts is "all". Handle malformed open-editor URLs with a controlled response and parse their query without relying on the Host header. (by @​bjohansebas in #​5772)

v5.2.6

Compare Source

Patch Changes

  • fix: allow undefined as the Server constructor options argument again (by @​bjohansebas in #​5695)

    Restores accepting undefined (defaulting it to {}) for the options
    argument, so passing a webpack config's optional devServer field type-checks and works as before.

  • Protect the built-in state-changing routes (/webpack-dev-server/invalidate and /webpack-dev-server/open-editor) against cross-site request forgery. Requests are now checked with Sec-Fetch-Site (falling back to an Origin/Host comparison when it is absent), so a cross-site page can no longer trigger a rebuild or open a file in the editor. Same-origin requests, user-initiated navigations, and non-browser clients (e.g. curl) are unaffected. (by @​bjohansebas in #​5698)

  • Handle malformed Host and Origin header values gracefully when validating requests. (by @​bjohansebas in #​5699)

v5.2.5

Compare Source

Patch Changes
  • Skip the HMR WebSocket path when forwarding upgrade requests to user-defined proxies, so custom proxy WebSocket upgrades are no longer intercepted by the dev server. (by @​bjohansebas in #​5680)

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

5.2.4 (2026-05-11)
Bug Fixes
  • set Cross-Origin-Resource-Policy header to prevent source code theft over HTTP
5.2.3 (2026-01-12)
Bug Fixes
  • add cause for errorObject (#​5518) (37b033d)
  • compatibility with event target and universal target and lazy compilation (574026c)
  • overlay: add ESC key to dismiss overlay (#​5598) (f91baa8)
  • progress indicator styles (#​5557) (41a53a1)
  • upgrade selfsigned to v5
5.2.2 (2025-06-03)
Bug Fixes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [webpack-dev-server](https://github.com/webpack/webpack-dev-server) | devDependencies | major | [`^5.2.4` → `^6.0.0`](https://renovatebot.com/diffs/npm/webpack-dev-server/5.2.4/6.1.0) | --- ### Release Notes <details> <summary>webpack/webpack-dev-server (webpack-dev-server)</summary> ### [`v6.1.0`](https://github.com/webpack/webpack-dev-server/blob/HEAD/CHANGELOG.md#610) [Compare Source](https://github.com/webpack/webpack-dev-server/compare/v6.0.0...v6.1.0) ##### Minor Changes - Run as a plugin from the top-level `plugins` of a multi-configuration, serving every configuration from one server. (by [@&#8203;alexander-akait](https://github.com/alexander-akait) in [#&#8203;5765](https://github.com/webpack/webpack-dev-server/pull/5765)) - Fix client progress modes, socket URL credentials, overlay and progress lifecycles, server startup error handling and local IP lookup; export `BaseServer`. (by [@&#8203;alexander-akait](https://github.com/alexander-akait) in [#&#8203;5739](https://github.com/webpack/webpack-dev-server/pull/5739)) - The browser client, the error overlay and both transports now come from webpack-dev-middleware, so this package has no client code of its own. Every option keeps its name and meaning, `allowedHosts` and the origin checks still apply here, and this server's `{ type }` messages are still sent next to the middleware's, so React Refresh keeps working. `client/index.js`, `client/socket.js` and `client/clients/WebSocketClient.js` still resolve while the client's internal files are gone, and the console wording, the overlay and the progress indicator are now the middleware's. `client.webSocketTransport: "sse"` adds Server-Sent Events, a universal build now runs in Node without the client throwing, and `sendMessage()`, `getClientEntry()` and `getClientHotEntry()` still work, a subclass's overrides included, but are deprecated. (by [@&#8203;alexander-akait](https://github.com/alexander-akait) in [#&#8203;5750](https://github.com/webpack/webpack-dev-server/pull/5750)) ##### Patch Changes - Keep hot and live reload working after a cancelled "Leave site?" dialog. (by [@&#8203;alexander-akait](https://github.com/alexander-akait) in [#&#8203;5744](https://github.com/webpack/webpack-dev-server/pull/5744)) - Keep the overlay for a runtime error thrown while the page is still loading. (by [@&#8203;alexander-akait](https://github.com/alexander-akait) in [#&#8203;5745](https://github.com/webpack/webpack-dev-server/pull/5745)) - Validate the `Host` and `Origin` headers and enforce same-origin checks on WebSocket upgrade requests handled by proxies with `ws: true`. This prevents cross-origin pages from connecting to proxied WebSocket services through the development server. (by [@&#8203;UlisesGascon](https://github.com/UlisesGascon) in [`cb1534a`](https://github.com/webpack/webpack-dev-server/commit/cb1534a097f21cf611995d70d83eb4ead69d1b64)) - Validate options with a precompiled schema to cut \~115ms from startup. (by [@&#8203;alexander-akait](https://github.com/alexander-akait) in [#&#8203;5746](https://github.com/webpack/webpack-dev-server/pull/5746)) - Validate Host and HTTP/2 authority headers independently of Origin protocol exceptions, including when `allowedHosts` is `"all"`. Handle malformed open-editor URLs with a controlled response and parse their query without relying on the Host header. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5771](https://github.com/webpack/webpack-dev-server/pull/5771)) ### [`v6.0.0`](https://github.com/webpack/webpack-dev-server/blob/HEAD/CHANGELOG.md#600) [Compare Source](https://github.com/webpack/webpack-dev-server/compare/v5.2.7...v6.0.0) ##### Major Changes - Bump Express to v5. See the [Express 5 migration guide](https://expressjs.com/en/guide/migrating-5.html) for the full list of breaking changes. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Bump the `webpack` peer dependency range from `^5.0.0` to `^5.101.0`. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Drop support for Node.js < 22.15.0. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Convert the source to native ES modules. The package keeps `"type": "module"` and now exposes both an ESM and a CommonJS build via the `exports` field: ESM consumers `import` the native `lib/`, while CommonJS consumers `require()` a transpiled `dist/` build — so the package works from both ESM and CommonJS, including environments where `require(ESM)` is not supported. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Remove CLI flags. Use the `serve` command from `webpack-cli` together with a configuration file or the programmatic API instead. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Remove the `internalIP` and `internalIPSync` static methods from `Server`. Resolve the local IP yourself if you need it. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Remove the `bypass` option from proxy configuration. Use the `router` or `context` options provided by `http-proxy-middleware` instead. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Remove SockJS support. The `webSocketServer` option no longer accepts `"sockjs"`; use the default `"ws"` transport instead. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Remove the `spdy` dependency. Use the built-in `node:http2` module via the `server` option for HTTP/2 support. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Update `http-proxy-middleware` to v4. See the [http-proxy-middleware v3 release notes](https://github.com/chimurai/http-proxy-middleware/releases/tag/v3.0.0) and [v4 release notes](https://github.com/chimurai/http-proxy-middleware/releases/tag/v4.0.0) for the full list of breaking changes. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Update `webpack-dev-middleware` to v8 and sync `originalUrl` for middleware compatibility. `server.middleware.getFilenameFromUrl()` is now asynchronous and resolves to `{ filename, extra: { stats, outputFileSystem } }`. See the [webpack-dev-middleware v8 release notes](https://github.com/webpack/webpack-dev-middleware/releases/tag/v8.0.0) for details. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) ##### Minor Changes - Add plugin support. `webpack-dev-server` can now be used as a webpack plugin, integrating with the compiler lifecycle without explicitly passing a compiler, preventing multiple server starts on recompilation, ensuring clean shutdown, and supporting `MultiCompiler` setups with multiple independent plugin servers. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Enable the compression middleware for HTTP/2 connections. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Remove the `colorette` dependency in favor of native ANSI styling. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Update `chokidar` to v5 and extend `watchFiles.options.ignored` to support glob string patterns via `tinyglobby`. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Use `compiler.platform` to determine the target environment instead of inspecting the resolved `target` string. Universal targets (`"universal"` or `["web", "node"]`, where `compiler.platform.universal` is `true` since webpack `5.108.0`) are treated as web targets so the client runtime is injected. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Use the WHATWG `URL` API instead of the deprecated `url.parse`. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) ##### Patch Changes - Bump production dependencies, notably `open` to v11 and `p-retry` to v8. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Reject cross-site requests to the internal `open-editor` and `invalidate` endpoints. They performed state-changing actions (opening a file in the editor, forcing a recompilation) on any GET request, so a page the developer visited could trigger them. They now require a same-origin request, validated via `Sec-Fetch-Site` with an `Origin`/`Host` fallback. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5691](https://github.com/webpack/webpack-dev-server/pull/5691)) - Treat loopback aliases (`127.0.0.1`, `::1`, `localhost`) as equivalent in `isSameOrigin` so the WebSocket client does not reject valid same-origin connections. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Migrate the test suite from Jest to `node:test` and set up the jsdom environment. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) - Update `webpack-cli` to v7.0.2. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5674](https://github.com/webpack/webpack-dev-server/pull/5674)) ### [`v5.2.7`](https://github.com/webpack/webpack-dev-server/releases/tag/v5.2.7) [Compare Source](https://github.com/webpack/webpack-dev-server/compare/v5.2.6...v5.2.7) ##### Patch Changes - Validate the `Host` and `Origin` headers and enforce same-origin checks on WebSocket upgrade requests handled by proxies with `ws: true`. This prevents cross-origin pages from connecting to proxied WebSocket services through the development server. (by [@&#8203;github-actions](https://github.com/apps/github-actions) in [#&#8203;5766](https://github.com/webpack/webpack-dev-server/pull/5766)) - Validate Host and HTTP/2 authority headers independently of Origin protocol exceptions, including when `allowedHosts` is `"all"`. Handle malformed open-editor URLs with a controlled response and parse their query without relying on the Host header. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5772](https://github.com/webpack/webpack-dev-server/pull/5772)) ### [`v5.2.6`](https://github.com/webpack/webpack-dev-server/releases/tag/v5.2.6) [Compare Source](https://github.com/webpack/webpack-dev-server/compare/v5.2.5...v5.2.6) ##### Patch Changes - fix: allow `undefined` as the `Server` constructor `options` argument again (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5695](https://github.com/webpack/webpack-dev-server/pull/5695)) Restores accepting `undefined` (defaulting it to `{}`) for the `options` argument, so passing a webpack config's optional `devServer` field type-checks and works as before. - Protect the built-in state-changing routes (`/webpack-dev-server/invalidate` and `/webpack-dev-server/open-editor`) against cross-site request forgery. Requests are now checked with `Sec-Fetch-Site` (falling back to an `Origin`/`Host` comparison when it is absent), so a cross-site page can no longer trigger a rebuild or open a file in the editor. Same-origin requests, user-initiated navigations, and non-browser clients (e.g. curl) are unaffected. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5698](https://github.com/webpack/webpack-dev-server/pull/5698)) - Handle malformed `Host` and `Origin` header values gracefully when validating requests. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5699](https://github.com/webpack/webpack-dev-server/pull/5699)) ### [`v5.2.5`](https://github.com/webpack/webpack-dev-server/blob/HEAD/CHANGELOG.md#525) [Compare Source](https://github.com/webpack/webpack-dev-server/compare/v5.2.4...v5.2.5) ##### Patch Changes - Skip the HMR WebSocket path when forwarding upgrade requests to user-defined proxies, so custom proxy WebSocket upgrades are no longer intercepted by the dev server. (by [@&#8203;bjohansebas](https://github.com/bjohansebas) in [#&#8203;5680](https://github.com/webpack/webpack-dev-server/pull/5680)) All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines. ##### [5.2.4](https://github.com/webpack/webpack-dev-server/compare/v5.2.3...v5.2.4) (2026-05-11) ##### Bug Fixes - set Cross-Origin-Resource-Policy header to prevent source code theft over HTTP ##### [5.2.3](https://github.com/webpack/webpack-dev-server/compare/v5.2.2...v5.2.3) (2026-01-12) ##### Bug Fixes - add `cause` for `errorObject` ([#&#8203;5518](https://github.com/webpack/webpack-dev-server/issues/5518)) ([37b033d](https://github.com/webpack/webpack-dev-server/commit/37b033da2c48335178495a1987c469a26ef3de60)) - compatibility with event target and universal target and lazy compilation ([574026c](https://github.com/webpack/webpack-dev-server/commit/574026c44b9c51f0bbd2f5a2836c54607289a071)) - **overlay:** add ESC key to dismiss overlay ([#&#8203;5598](https://github.com/webpack/webpack-dev-server/issues/5598)) ([f91baa8](https://github.com/webpack/webpack-dev-server/commit/f91baa8831e061e2998849966b8002b40b83fb07)) - progress indicator styles ([#&#8203;5557](https://github.com/webpack/webpack-dev-server/issues/5557)) ([41a53a1](https://github.com/webpack/webpack-dev-server/commit/41a53a1accdb0a90785d82cbe8a079794eeed3c8)) - upgrade selfsigned to v5 ##### [5.2.2](https://github.com/webpack/webpack-dev-server/compare/v5.2.1...v5.2.2) (2025-06-03) ##### Bug Fixes - "Overlay enabled" false positive ([18e72ee](https://github.com/webpack/webpack-dev-server/commit/18e72ee3e57a6e7598a6c068c0ff7c7bb6a857f1)) - do not crush when error is null for runtime errors ([#&#8203;5447](https://github.com/webpack/webpack-dev-server/issues/5447)) ([309991f](https://github.com/webpack/webpack-dev-server/commit/309991f947baa0354140b9930a9654ac792e20c4)) - remove unnecessary header `X_TEST` ([#&#8203;5451](https://github.com/webpack/webpack-dev-server/issues/5451)) ([64a6124](https://github.com/webpack/webpack-dev-server/commit/64a6124bf1b4d158bb42a4341dd03121ae3759fa)) - respect the `allowedHosts` option for cross-origin header check ([#&#8203;5510](https://github.com/webpack/webpack-dev-server/issues/5510)) ([03d1214](https://github.com/webpack/webpack-dev-server/commit/03d12141bf7be09dfb14e91e5c834ee63bd9a9a2)) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xOTcuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE5Ny4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Update dependency webpack-dev-server to v6
Some checks failed
Build & deploy / Build & publish server image (pull_request) Has been skipped
Details
renovate/artifacts Artifact file update failure
Build & deploy / Build & deploy website (pull_request) Failing after 42s
Details
aeaefee6f3
andras commented 2026-10-31 06:10:21 +00:00
Author
Owner

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: webpack-cli@7.0.3
npm error Found: webpack-dev-server@6.1.0
npm error node_modules/webpack-dev-server
npm error   dev webpack-dev-server@"^6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional webpack-dev-server@"^5.0.0" from webpack-cli@7.0.3
npm error node_modules/webpack-cli
npm error   dev webpack-cli@"^7.0.3" from the root project
npm error
npm error Conflicting peer dependency: webpack-dev-server@5.2.7
npm error node_modules/webpack-dev-server
npm error   peerOptional webpack-dev-server@"^5.0.0" from webpack-cli@7.0.3
npm error   node_modules/webpack-cli
npm error     dev webpack-cli@"^7.0.3" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-10-31T06_10_19_574Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-10-31T06_10_19_574Z-debug-0.log
### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: frontend/package-lock.json ``` npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: webpack-cli@7.0.3 npm error Found: webpack-dev-server@6.1.0 npm error node_modules/webpack-dev-server npm error dev webpack-dev-server@"^6.0.0" from the root project npm error npm error Could not resolve dependency: npm error peerOptional webpack-dev-server@"^5.0.0" from webpack-cli@7.0.3 npm error node_modules/webpack-cli npm error dev webpack-cli@"^7.0.3" from the root project npm error npm error Conflicting peer dependency: webpack-dev-server@5.2.7 npm error node_modules/webpack-dev-server npm error peerOptional webpack-dev-server@"^5.0.0" from webpack-cli@7.0.3 npm error node_modules/webpack-cli npm error dev webpack-cli@"^7.0.3" from the root project npm error npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /tmp/renovate/cache/others/npm/_logs/2026-10-31T06_10_19_574Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-10-31T06_10_19_574Z-debug-0.log ```
Some checks failed
Build & deploy / Build & publish server image (pull_request) Has been skipped
Details
renovate/artifacts Artifact file update failure
Build & deploy / Build & deploy website (pull_request) Failing after 42s
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin "renovate/webpack-dev-server-6.x:renovate/webpack-dev-server-6.x"
git switch "renovate/webpack-dev-server-6.x"

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch "main"
git merge --no-ff "renovate/webpack-dev-server-6.x"
git switch "renovate/webpack-dev-server-6.x"
git rebase "main"
git switch "main"
git merge --ff-only "renovate/webpack-dev-server-6.x"
git switch "renovate/webpack-dev-server-6.x"
git rebase "main"
git switch "main"
git merge --no-ff "renovate/webpack-dev-server-6.x"
git switch "main"
git merge --squash "renovate/webpack-dev-server-6.x"
git switch "main"
git merge --ff-only "renovate/webpack-dev-server-6.x"
git switch "main"
git merge "renovate/webpack-dev-server-6.x"
git push origin "main"
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
dependencies
Pull requests that update a dependency file

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
andras/decla-red!24
No description provided.