chore(deps): Bump webpack-dev-server from 5.2.6 to 6.0.0 in /DNNPlatform/Portals/_default/Skins/Bootstrap 4 Instant

[dependabot]

Bumps webpack-dev-server from 5.2.6 to 6.0.0.

Release notes

Sourced from webpack-dev-server's releases.

v6.0.0

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, allowing the package to be consumed from both ESM and CommonJS without relying on require(ESM) for CommonJS consumers. (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)

... (truncated)

Changelog

Sourced from webpack-dev-server's changelog.

6.0.0

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)

... (truncated)

Commits

• 05cb792 chore(release): new release (#5692)
• a451839 fix: handle middleware teardown in plugin mode (#5703)
• c2d23a7 fix: load ESM-only dependencies with native import() in the CommonJS build (#...
• ba54764 fix: reject cross-site requests to open-editor and invalidate endpoints (#5691)
• 2b369b3 fixup!
• 08a0ea7 fix: ensure undefined options default to an empty object in Server constructor
• 797b9e7 fix: handle undefined options in Server constructor
• e90221c feat: plugin support (#5650)
• 4c351e1 feat: support universal platform as a web target (#5690)
• 2236aa4 chore: update http-proxy-middleware to version 4.1.1 and add tests for pathRe...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[jsboige]

HOLD — majeure non validée dans un arbre vendoré (pas un refus, une décision de politique en attente)

Ses trois voisines de ce lot viennent d'être mergées (#898 json5, #899 + #900 loader-utils) : correctifs de sécurité, package-lock.json seul, arbre vendoré → risque nul, bénéfice clair.

Celle-ci est différente sur deux points :

1. Bump majeur (webpack-dev-server 5.2.6 → 6.0.0), pas un patch de sécurité — le titre est chore(deps), pas un avis.
2. Elle touche package.json, pas seulement le lockfile — elle modifie les dépendances déclarées du skin, pas juste l'arbre résolu.

Le skin Portals/_default/Skins/Bootstrap 4 Instant/ est vendoré avec son dist/ pré-buildé, et la CI de ce dépôt est du dotnet build — donc rien ne valide ce bump, ni ne le consomme. « Inerte » coupe dans les deux sens : ça retire le risque, mais ça retire aussi le bénéfice, et ça laisse une majeure non testée dans l'historique.

Pourquoi ne pas simplement fermer non plus : sur les 34 PRs Dependabot traitées aujourd'hui, la quasi-totalité était du bruit de lockfile vendoré — mais deux portaient du vrai contenu (#871, 28 advisories réellement purgées ; #887, une bascule de licence MIT → RPL-1.5 qui aurait cassé la pureté MIT du dépôt). Le tapis roulant noie le signal, et la réponse n'est pas de trancher au réflexe dans un sens ou dans l'autre.

Cette PR est l'exemple canonique de ce que la configuration doit régler : un brouillon .github/dependabot.yml est en cours côté myia-po-2024 (groups: pour agréger les lockfiles vendorés + ignore ciblés). Modifier la discipline Dependabot du dépôt demande un arbitrage jsboige — il est dans ma liste d'attente.

En attente donc de : la décision sur dependabot.yml. Si la politique retenue ignore les majeures dev-only dans les arbres vendorés, celle-ci se ferme d'elle-même. Si elle les accepte, elle se merge sans plus de discussion. Dans les deux cas la décision sera explicite au lieu d'être un réflexe.

Pas de CHANGES_REQUESTED : rien à corriger dans la PR elle-même.

🤖 Coordinator ai-01

[jsboige]

Fermée out-of-policy au titre de la politique dependabot arbitrée par jsboige (option A) et mergée en #910 (05e12463).

Pourquoi cette PR ne sera pas reprise telle quelle : DNNPlatform/Portals/_default/Skins/Bootstrap 4 Instant est un arbre npm vendored — du code tiers embarqué dans le dépôt DNN, pas une dépendance que nous construisons. La politique retenue pour ces 26 arbres est surveiller, groupé, majors ignorés :

• groups → un seul PR par arbre au lieu de N (plafond ≤ 26 PR/semaine au global au lieu de plusieurs centaines) ;
• ignore: version-update:semver-major → un major sur un arbre vendored (ici webpack-dev-server 5→6 : Express 5, Node ≥ 22.15, passage ESM natif) n'est pas une mise à jour de sécurité, c'est une migration d'outillage de build d'un skin que nous ne construisons pas.

Les patches et minors de sécurité sur ces mêmes arbres continuent d'arriver — c'est précisément ce que « surveiller » veut dire. Seuls les majors sont filtrés.

Si un jour un CVE ne se corrige que par un major sur un arbre vendored, la marche à suivre est de retirer ponctuellement l'ignore de cet arbre-là dans .github/dependabot.yml, pas de merger un major à l'aveugle.

Réf : politique #910 · roadmap #458.

🤖 Coordinator ai-01

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.