[agent] Failed to update webpack-dev-server

[claude]

Failed dependency update

Package: webpack-dev-server
From: 5.2.4 → To: 6.0.0

Error

No validation step failed — the update was reverted because it would ship a peerDependencies range that provably conflicts with the package's own dependency tree.

syncpack fix propagated the bump into @squide/firefly-webpack-configs:

   "peerDependencies": {
-    "webpack-dev-server": "^5.2.4"
+    "webpack-dev-server": "^6.0.0"
   },

But @squide/firefly-webpack-configs depends on @workleap/webpack-configs@^1.6.15, which still requires webpack-dev-server@^5.2.4. pnpm peers check reports:

✕ unmet peer webpack-dev-server
  Installed: 6.0.0
  Wanted:
    ^5.2.4:
      @workleap/webpack-configs@1.6.15
    "^4.8.0 || 5.x":
      @pmmmwh/react-refresh-webpack-plugin@0.6.2

Publishing that peer range would force every consumer of @squide/firefly-webpack-configs onto webpack-dev-server@6 while the shared Workleap webpack config it wraps — and the React Refresh plugin that config uses — both cap at 5.x. There is no version a consumer could install that satisfies all three.

What was tried

• Verified webpack-dev-server@6 itself is not broken: started pnpm dev-basic-webpack and validated the basic-webpack sample in a real browser. The host boots on :8086 (remotes on :8087/:8088), the mock login (temp/temp) succeeds, the home page and the full federated navigation render, and there are zero console errors or page errors.
• Confirmed pnpm lint and pnpm test also pass with webpack-dev-server@6, so this is purely a published-peer-range problem, not a runtime or build regression.
• Considered shipping it as a major changeset for @squide/firefly-webpack-configs. Rejected: a major release does not make the peer graph satisfiable, it just relabels a broken constraint. The conflict has to be resolved upstream first.
• Reverted webpack-dev-server to 5.2.4 in @squide/firefly-webpack-configs (both peerDependencies ^5.2.4 and devDependencies 5.2.4) and in the four samples/basic-webpack/* packages. All remaining updates then validated successfully.

Unblocking this

This needs @workleap/webpack-configs to widen its webpack-dev-server peer range to include ^6.0.0 (which in turn likely needs @pmmmwh/react-refresh-webpack-plugin to support 6.x). Once that lands, re-running the dependency update should carry webpack-dev-server@6 through cleanly — and it should then be released as a major bump of @squide/firefly-webpack-configs, since the peer range narrowing drops webpack-dev-server@5 support for consumers.

Workflow run

https://github.com/workleap/wl-squide/actions/runs/30370554419