Update dependency webpack-dev-middleware to v7 [SECURITY]

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
webpack-dev-middleware	^1.9.0 → ^7.0.0

---

Path traversal in webpack-dev-middleware

CVE-2024-29180 / GHSA-wr3j-pwj9-hqq6

More information

Details

Summary

The webpack-dev-middleware middleware does not validate the supplied URL address sufficiently before returning the local file. It is possible to access any file on the developer's machine.

Details

The middleware can either work with the physical filesystem when reading the files or it can use a virtualized in-memory memfs filesystem.
If writeToDisk configuration option is set to true, the physical filesystem is used:
https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/setupOutputFileSystem.js#L21

The getFilenameFromUrl method is used to parse URL and build the local file path.
The public path prefix is stripped from the URL, and the unsecaped path suffix is appended to the outputPath:
https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/getFilenameFromUrl.js#L82
As the URL is not unescaped and normalized automatically before calling the midlleware, it is possible to use %2e and %2f sequences to perform path traversal attack.

PoC

A blank project can be created containing the following configuration file webpack.config.js:
module.exports = { devServer: { devMiddleware: { writeToDisk: true } } };

When started, it is possible to access any local file, e.g. /etc/passwd:
$ curl localhost:8080/public/..%2f..%2f..%2f..%2f../etc/passwd

root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin

Impact

The developers using webpack-dev-server or webpack-dev-middleware are affected by the issue. When the project is started, an attacker might access any file on the developer's machine and exfiltrate the content (e.g. password, configuration files, private source code, ...).

If the development server is listening on a public IP address (or 0.0.0.0), an attacker on the local network can access the local files without any interaction from the victim (direct connection to the port).

If the server allows access from third-party domains (CORS, Allow-Access-Origin: * ), an attacker can send a malicious link to the victim. When visited, the client side script can connect to the local server and exfiltrate the local files.

Recommendation

The URL should be unescaped and normalized before any further processing.

Severity

• CVSS Score: 7.4 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

References

• https://github.com/webpack/webpack-dev-middleware/security/advisories/GHSA-wr3j-pwj9-hqq6
• https://nvd.nist.gov/vuln/detail/CVE-2024-29180
• https://github.com/webpack/webpack-dev-middleware/commit/189c4ac7d2344ec132a4689e74dc837ec5be0132
• https://github.com/webpack/webpack-dev-middleware/commit/9670b3495da518fe667ff3428c5e4cb9f2f3d353
• https://github.com/webpack/webpack-dev-middleware/commit/e10008c762e4d5821ed6990348dabf0d4d93a10e
• https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/getFilenameFromUrl.js#L82
• https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/setupOutputFileSystem.js#L21
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v5.3.4
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v6.1.2
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v7.1.0
• https://github.com/advisories/GHSA-wr3j-pwj9-hqq6

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

webpack-dev-middleware vulnerable to Path Traversal via non-slash-terminated publicPath

CVE-2026-76844 / GHSA-g84c-rxfj-3j2c

More information

Details

[!IMPORTANT]
CVE-2026-76844 was assigned and published for this issue by VulnCheck on 2026-08-24 without prior coordination with the webpack maintainers or the OpenJS Foundation, which holds the CVE Numbering Authority scope for webpack projects. Neither the maintainers nor the OpenJS CNA were notified before publication, and no fix was available at that time. This advisory is the coordinated record produced by the webpack maintainers and the OpenJS Foundation CNA.

Impact

webpack-dev-middleware resolves a request to a local file in getFilenameFromUrl. When the configured publicPath has no trailing slash (for example /assets), a request that shares that prefix without being under it (for example /assets../secret) still passes the containment check, and the .. guard does not catch it because it runs on the path before the publicPath prefix is stripped. The stripped remainder then escapes the configured output directory once joined, so an unauthenticated request can read files outside the output root. Applications serving webpack-dev-middleware (directly or via webpack-dev-server) with a publicPath that does not end in a slash are affected. A development server reachable on the network can be attacked with a single request and no victim interaction.

Patches

Patched in webpack-dev-middleware 8.3.0. There is no backport to the 5.x, 6.x, or 7.x lines; users on those lines should upgrade to 8.3.0 or later.

Workarounds

Configure publicPath with a trailing slash (for example /assets/ instead of /assets), or upgrade to a patched version.

References

• CVE-2024-29180 (GHSA-wr3j-pwj9-hqq6), the earlier path traversal in the same component that this issue bypasses.

Severity

• CVSS Score: 7.4 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

References

• https://github.com/webpack/webpack-dev-middleware/security/advisories/GHSA-g84c-rxfj-3j2c
• https://nvd.nist.gov/vuln/detail/CVE-2026-76844
• https://github.com/webpack/webpack-dev-middleware/pull/2404
• https://github.com/webpack/webpack-dev-middleware/commit/13344e78b26d88fe9b7c8381a3860e248a52359b
• https://github.com/webpack/webpack-dev-middleware/commit/cefccbac330c29052fc6dffe85fd292ea2ac782b
• https://github.com/advisories/GHSA-wr3j-pwj9-hqq6
• https://github.com/webpack/webpack-dev-middleware/blob/v8.1.1/src/middleware.js
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v7.4.6
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v8.3.0
• https://www.vulncheck.com/advisories/webpack-dev-middleware-path-traversal-via-offset-slice-on-a-non-slash-terminated-publicpath
• https://github.com/advisories/GHSA-g84c-rxfj-3j2c

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Path traversal in webpack-dev-middleware

CVE-2024-29180 / CVE-2026-76844 / GHSA-g84c-rxfj-3j2c / GHSA-wr3j-pwj9-hqq6

More information

Details

Summary

The webpack-dev-middleware middleware does not validate the supplied URL address sufficiently before returning the local file. It is possible to access any file on the developer's machine.

Details

The middleware can either work with the physical filesystem when reading the files or it can use a virtualized in-memory memfs filesystem.
If writeToDisk configuration option is set to true, the physical filesystem is used:
https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/setupOutputFileSystem.js#L21

The getFilenameFromUrl method is used to parse URL and build the local file path.
The public path prefix is stripped from the URL, and the unsecaped path suffix is appended to the outputPath:
https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/getFilenameFromUrl.js#L82
As the URL is not unescaped and normalized automatically before calling the midlleware, it is possible to use %2e and %2f sequences to perform path traversal attack.

PoC

A blank project can be created containing the following configuration file webpack.config.js:
module.exports = { devServer: { devMiddleware: { writeToDisk: true } } };

When started, it is possible to access any local file, e.g. /etc/passwd:
$ curl localhost:8080/public/..%2f..%2f..%2f..%2f../etc/passwd

root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin

Impact

The developers using webpack-dev-server or webpack-dev-middleware are affected by the issue. When the project is started, an attacker might access any file on the developer's machine and exfiltrate the content (e.g. password, configuration files, private source code, ...).

If the development server is listening on a public IP address (or 0.0.0.0), an attacker on the local network can access the local files without any interaction from the victim (direct connection to the port).

If the server allows access from third-party domains (CORS, Allow-Access-Origin: * ), an attacker can send a malicious link to the victim. When visited, the client side script can connect to the local server and exfiltrate the local files.

Recommendation

The URL should be unescaped and normalized before any further processing.

Severity

• CVSS Score: 7.4 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

References

• https://github.com/webpack/webpack-dev-middleware/security/advisories/GHSA-wr3j-pwj9-hqq6
• https://nvd.nist.gov/vuln/detail/CVE-2024-29180
• https://github.com/webpack/webpack-dev-middleware/commit/189c4ac7d2344ec132a4689e74dc837ec5be0132
• https://github.com/webpack/webpack-dev-middleware/commit/9670b3495da518fe667ff3428c5e4cb9f2f3d353
• https://github.com/webpack/webpack-dev-middleware/commit/e10008c762e4d5821ed6990348dabf0d4d93a10e
• https://github.com/webpack/webpack-dev-middleware
• https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/getFilenameFromUrl.js#L82
• https://github.com/webpack/webpack-dev-middleware/blob/7ed24e0b9f53ad1562343f9f517f0f0ad2a70377/src/utils/setupOutputFileSystem.js#L21
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v5.3.4
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v6.1.2
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v7.1.0

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

webpack-dev-middleware vulnerable to Path Traversal via non-slash-terminated publicPath

CVE-2024-29180 / CVE-2026-76844 / GHSA-g84c-rxfj-3j2c / GHSA-wr3j-pwj9-hqq6

More information

Details

[!IMPORTANT]
CVE-2026-76844 was assigned and published for this issue by VulnCheck on 2026-08-24 without prior coordination with the webpack maintainers or the OpenJS Foundation, which holds the CVE Numbering Authority scope for webpack projects. Neither the maintainers nor the OpenJS CNA were notified before publication, and no fix was available at that time. This advisory is the coordinated record produced by the webpack maintainers and the OpenJS Foundation CNA.

Impact

webpack-dev-middleware resolves a request to a local file in getFilenameFromUrl. When the configured publicPath has no trailing slash (for example /assets), a request that shares that prefix without being under it (for example /assets../secret) still passes the containment check, and the .. guard does not catch it because it runs on the path before the publicPath prefix is stripped. The stripped remainder then escapes the configured output directory once joined, so an unauthenticated request can read files outside the output root. Applications serving webpack-dev-middleware (directly or via webpack-dev-server) with a publicPath that does not end in a slash are affected. A development server reachable on the network can be attacked with a single request and no victim interaction.

Patches

Patched in webpack-dev-middleware 8.3.0. There is no backport to the 5.x, 6.x, or 7.x lines; users on those lines should upgrade to 8.3.0 or later.

Workarounds

Configure publicPath with a trailing slash (for example /assets/ instead of /assets), or upgrade to a patched version.

References

• CVE-2024-29180 (GHSA-wr3j-pwj9-hqq6), the earlier path traversal in the same component that this issue bypasses.

Severity

• CVSS Score: 7.4 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

References

• https://github.com/webpack/webpack-dev-middleware/security/advisories/GHSA-g84c-rxfj-3j2c
• https://nvd.nist.gov/vuln/detail/CVE-2026-76844
• https://github.com/webpack/webpack-dev-middleware/pull/2404
• https://github.com/webpack/webpack-dev-middleware/commit/13344e78b26d88fe9b7c8381a3860e248a52359b
• https://github.com/webpack/webpack-dev-middleware/commit/cefccbac330c29052fc6dffe85fd292ea2ac782b
• https://github.com/advisories/GHSA-wr3j-pwj9-hqq6
• https://github.com/webpack/webpack-dev-middleware
• https://github.com/webpack/webpack-dev-middleware/blob/v8.1.1/src/middleware.js
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v7.4.6
• https://github.com/webpack/webpack-dev-middleware/releases/tag/v8.3.0
• https://www.vulncheck.com/advisories/webpack-dev-middleware-path-traversal-via-offset-slice-on-a-non-slash-terminated-publicpath

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

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

v7.4.6

Compare Source

7.4.6 (2026-09-03)

Bug Fixes

• reject requests that resolve outside the output directory

v7.4.5

Compare Source

v7.4.4

Compare Source

v7.4.3

Compare Source

v7.4.2

Compare Source

v7.4.1

Compare Source

v7.4.0

Compare Source

Features

• added the cacheImmutable option to cache immutable assets (assets with a hash in file name like image.e12ab567.jpg) (5ed629d)
• allow to configure the Cache-Control header (#​1923) (f7529c3)

Bug Fixes

• support devServer: false (b443f4d)

v7.3.0

Compare Source

Features

• support hono (#​1890) (0f9f398)

7.2.1 (2024-04-02)

Bug Fixes

• avoid extra log

v7.2.1

Compare Source

Features

• support hono (#​1890) (0f9f398)

7.2.1 (2024-04-02)

Bug Fixes

• avoid extra log

v7.2.0

Compare Source

Features

• support hono (#​1890) (0f9f398)

7.2.1 (2024-04-02)

Bug Fixes

• avoid extra log

v7.1.1

Compare Source

Features

• hapi support (b3f9126)
• koa support (#​1792) (458c17c)
• support ETag header generation (#​1797) (b759181)
• support Last-Modified header generation (#​1798) (18e5683)

7.1.1 (2024-03-21)

Bug Fixes

• ContentLength incorrectly set for empty files (#​1785) (0f3e25e)
• improve perf (#​1777) (5b47c92)
• types: make types better (#​1786) (e4d183e)

v7.1.0

Compare Source

Features

• hapi support (b3f9126)
• koa support (#​1792) (458c17c)
• support ETag header generation (#​1797) (b759181)
• support Last-Modified header generation (#​1798) (18e5683)

7.1.1 (2024-03-21)

Bug Fixes

• ContentLength incorrectly set for empty files (#​1785) (0f3e25e)
• improve perf (#​1777) (5b47c92)
• types: make types better (#​1786) (e4d183e)

v7.0.0

Compare Source

⚠ BREAKING CHANGES

• minimum supported Node.js version is 18.12.0 (#​1694)
• updated memfs@​4 (#​1693)

Features

• updated memfs@​4 (#​1693) (244d9f8)

• minimum supported Node.js version is 18.12.0 (#​1694) (e273d61)

6.1.1 (2023-05-16)

Bug Fixes

• types: methods should be string array (#​1550) (41b2f77)

v6.1.3

Compare Source

6.1.3 (2024-03-29)

Bug Fixes

• security problem (#​1799) (5a4d9e8)

v6.1.2

Compare Source

6.1.2 (2024-03-20)

Bug Fixes

• security: do not allow to read files above (#​1778) (9670b34)

v6.1.1

Compare Source

⚠ BREAKING CHANGES

• minimum supported Node.js version is 18.12.0 (#​1694)
• updated memfs@​4 (#​1693)

Features

• updated memfs@​4 (#​1693) (244d9f8)

• minimum supported Node.js version is 18.12.0 (#​1694) (e273d61)

6.1.1 (2023-05-16)

Bug Fixes

• types: methods should be string array (#​1550) (41b2f77)

v6.1.0

Compare Source

⚠ BREAKING CHANGES

• minimum supported Node.js version is 18.12.0 (#​1694)
• updated memfs@​4 (#​1693)

Features

• updated memfs@​4 (#​1693) (244d9f8)

• minimum supported Node.js version is 18.12.0 (#​1694) (e273d61)

6.1.1 (2023-05-16)

Bug Fixes

• types: methods should be string array (#​1550) (41b2f77)

v6.0.2

Compare Source

Features

• added mimeTypeDefault option (#​1527) (503d290)
• added modifyResponseData option (#​1529) (35dac70)

Bug Fixes

• don't use memory-fs when writeToDisk is true (#​1537) (852245e)
• faster startup time (f5f033b)

6.0.2 (2023-03-19)

Bug Fixes

• make webpack optional peerDep (#​1488) (81c39ba)

6.0.1 (2022-11-28)

Bug Fixes

• update schema for index and methods properties (#​1397) (cda328e)

v6.0.1

Compare Source

Features

• added mimeTypeDefault option (#​1527) (503d290)
• added modifyResponseData option (#​1529) (35dac70)

Bug Fixes

• don't use memory-fs when writeToDisk is true (#​1537) (852245e)
• faster startup time (f5f033b)

6.0.2 (2023-03-19)

Bug Fixes

• make webpack optional peerDep (#​1488) (81c39ba)

6.0.1 (2022-11-28)

Bug Fixes

• update schema for index and methods properties (#​1397) (cda328e)

v6.0.0

Compare Source

Features

• added mimeTypeDefault option (#​1527) (503d290)
• added modifyResponseData option (#​1529) (35dac70)

Bug Fixes

• don't use memory-fs when writeToDisk is true (#​1537) (852245e)
• faster startup time (f5f033b)

6.0.2 (2023-03-19)

Bug Fixes

• make webpack optional peerDep (#​1488) (81c39ba)

6.0.1 (2022-11-28)

Bug Fixes

• update schema for index and methods properties (#​1397) (cda328e)

v5.3.4

Compare Source

5.3.4 (2024-03-20)

Bug Fixes

• security: do not allow to read files above (#​1779) (189c4ac)

v5.3.3

Compare Source

⚠ BREAKING CHANGES

• minimum supported webpack version is 5.0.0
• minimum supported Nodejs version is 14.15.0

5.3.3 (2022-05-18)

Bug Fixes

• types for Request and Response (#​1271) (eeb8aa8)

5.3.2 (2022-05-17)

Bug Fixes

• node types (#​1195) (d68ab36)

5.3.1 (2022-02-01)

Bug Fixes

• types (#​1187) (0f82e1d)

v5.3.2

Compare Source

⚠ BREAKING CHANGES

• minimum supported webpack version is 5.0.0
• minimum supported Nodejs version is 14.15.0

5.3.3 (2022-05-18)

Bug Fixes

• types for Request and Response (#​1271) (eeb8aa8)

5.3.2 (2022-05-17)

Bug Fixes

• node types (#​1195) (d68ab36)

5.3.1 (2022-02-01)

Bug Fixes

• types (#​1187) (0f82e1d)

v5.3.1

Compare Source

⚠ BREAKING CHANGES

• minimum supported webpack version is 5.0.0
• minimum supported Nodejs version is 14.15.0

5.3.3 (2022-05-18)

Bug Fixes

• types for Request and Response (#​1271) (eeb8aa8)

5.3.2 (2022-05-17)

Bug Fixes

• node types (#​1195) (d68ab36)

5.3.1 (2022-02-01)

Bug Fixes

• types (#​1187) (0f82e1d)

v5.3.0

Compare Source

⚠ BREAKING CHANGES

• minimum supported webpack version is 5.0.0
• minimum supported Nodejs version is 14.15.0

5.3.3 (2022-05-18)

Bug Fixes

• types for Request and Response (#​1271) (eeb8aa8)

5.3.2 (2022-05-17)

Bug Fixes

• node types (#​1195) (d68ab36)

5.3.1 (2022-02-01)

Bug Fixes

• types (#​1187) (0f82e1d)

v5.2.2

Compare Source

Features

• added types (a2fa77f)
• removed cjs wrapper (#​1146) (b6d53d3)

5.2.2 (2021-11-17)

Chore

• update schema-utils package to 4.0.0 version

5.2.1 (2021-09-25)

• internal release, no visible changes and features

v5.2.1

Compare Source

Features

• added types (a2fa77f)
• removed cjs wrapper (#​1146) (b6d53d3)

5.2.2 (2021-11-17)

Chore

• update schema-utils package to 4.0.0 version

5.2.1 (2021-09-25)

• internal release, no visible changes and features

v5.2.0

Compare Source

Features

• added types (a2fa77f)
• removed cjs wrapper (#​1146) (b6d53d3)

5.2.2 (2021-11-17)

Chore

• update schema-utils package to 4.0.0 version

5.2.1 (2021-09-25)

• internal release, no visible changes and features

v5.1.0

Compare Source

Features

• don't read full file if Range header is present (e8b21f0)
• output more information on errors (#​1024) (7df9e44)

Bug Fixes

• reduced package size by removing mem package (#​1027) (0d55268)

v5.0.0

Compare Source

⚠ BREAKING CHANGES

• minimum supported Node.js version is 12.13.0 (#​928) (4cffeff)

v4.3.0

Compare Source

Features

• add getFilenameFromUrl to API (#​911) (1edc726)

Bug Fixes

• husky config (#​904) (8a423be)
• typo depandabot -> dependabot (#​905) (7062990)

v4.2.0

Compare Source

Features

• allow the headers option to accept function (#​897) (966afb3)

v4.1.0

Compare Source

Features

• added the stats option (376cdba)

4.0.4 (2021-01-13)

Bug Fixes

• compatibility with webpack@​4 (#​816) (acdfd4d)

4.0.3 (2021-01-12)

Bug Fixes

• output stats to stdout instead stderr, how does webpack-cli, if you need hide stats from output please use { stats: false } or { stats: 'none' } (4de0f97)
• colors are working for stats (4de0f97)
• schema description (#​783) (f9ce2b2)
• skip Content-type header on unknown types (#​809) (5c9eee5)

4.0.2 (2020-11-10)

Bug Fixes

• compatibility with the headers option (#​763) (7c4cac5)

4.0.1 (2020-11-09)

Bug Fixes

• compatibility with connect (b83a1db)

v4.0.4

Compare Source

Features

• added the stats option (376cdba)

4.0.4 (2021-01-13)

Bug Fixes

• compatibility with webpack@​4 (#​816) (acdfd4d)

4.0.3 (2021-01-12)

Bug Fixes

• output stats to stdout instead stderr, how does webpack-cli, if you need hide stats from output please use { stats: false } or { stats: 'none' } (4de0f97)
• colors are working for stats (4de0f97)
• schema description (#​783) (f9ce2b2)
• skip Content-type header on unknown types (#​809) (5c9eee5)

4.0.2 (2020-11-10)

Bug Fixes

• compatibility with the headers option (#​763) (7c4cac5)

4.0.1 (2020-11-09)

Bug Fixes

• compatibility with connect (b83a1db)

v4.0.3

Compare Source

Features

• added the stats option ([376cdba]

❗ Important

✂ PR body was truncated to here.

---

Configuration

📅 Schedule: (in timezone US/Eastern)

• 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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ 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: yarn.lock

/opt/containerbase/tools/corepack/0.28.0/14.18.2/node_modules/corepack/dist/yarn.js:2
process.env.COREPACK_ENABLE_DOWNLOAD_PROMPT??='1'
                                           ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1001:16)
    at Module._compile (internal/modules/cjs/loader.js:1049:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47

[renovate]

⚠️ 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: yarn.lock

/opt/containerbase/tools/corepack/0.36.0/14.18.2/node_modules/corepack/dist/yarn.js:2
process.env.COREPACK_ENABLE_DOWNLOAD_PROMPT??='1'
                                           ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1001:16)
    at Module._compile (internal/modules/cjs/loader.js:1049:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47

[sentry]

Bug: Upgrading webpack-dev-middleware to v5 while using webpack v4 will cause a runtime error, as v5 requires webpack v5. This will break the development server.
_{Severity: CRITICAL}

Suggested Fix

To resolve this incompatibility, either upgrade webpack to version 5.0.0 or higher to match the webpack-dev-middleware requirement, or find a version of webpack-dev-middleware that is compatible with webpack v4 and also contains the necessary security fix.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L132

Potential issue: The project upgrades `webpack-dev-middleware` to version `^5.0.0` but
continues to use `webpack` version `^4.46.0`. `webpack-dev-middleware` v5 has a peer
dependency on `webpack` v5 and is not backward compatible. When the development server
in `hot-reload-dev-server.js` initializes the middleware, it passes a `webpack` v4
compiler object. The middleware expects a `webpack` v5 compiler, and the mismatch in
APIs will cause a runtime error, preventing the development server from starting. This
will block all local development workflows.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: The webpack-dev-middleware v5 upgrade is incompatible with the project's webpack v4 without manual configuration, which will cause the development server to crash on startup.
_{Severity: CRITICAL}

Suggested Fix

To resolve the incompatibility, either upgrade webpack to v5, or manually configure the outputFileSystem for webpack-dev-middleware. If staying with webpack v4, you must provide an outputFileSystem instance that has the required .join() and mkdirp methods.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L132

Potential issue: The project's `webpack` version is `^4.46.0`, but
`webpack-dev-middleware` is being upgraded to v5. Version 5 of `webpack-dev-middleware`
is designed for `webpack` v5 and has breaking changes when used with `webpack` v4.
Specifically, it requires the `outputFileSystem` to have `.join()` and `mkdirp` methods,
which are not provided by default in the `webpack` v4 environment. Since the code does
not manually configure the `outputFileSystem`, the development server will fail to
start, preventing developers from running the application locally.

[sentry]

Bug: The upgrade of webpack-dev-middleware to v5 is incompatible with the project's existing webpack v4 dependency, which will break the development server.
_{Severity: CRITICAL}

Suggested Fix

To resolve this incompatibility, either upgrade webpack to version 5 alongside the webpack-dev-middleware upgrade, or revert the webpack-dev-middleware upgrade to a version compatible with webpack v4.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L132

Potential issue: The pull request updates `webpack-dev-middleware` to version 5.0.0
while `webpack` remains at version 4.46.0. `webpack-dev-middleware` v5 has a peer
dependency requirement for `webpack` v5. The development server, initiated via
`hot-reload-dev-server.js`, passes a `webpack` v4 compiler instance to the
`webpack-dev-middleware`. This will cause a runtime crash during initialization because
the middleware will attempt to use webpack v5 APIs that do not exist in webpack v4,
breaking the local development workflow.