ValidationError: Progress Plugin crash when webpack resolves to 5.106.2

[tambaqui]

Describe the bug

Running 10up-toolkit build (or start) fails immediately with a ValidationError
from webpack's ProgressPlugin when npm resolves webpack to 5.106.2.
The same setup works correctly with webpack 5.105.2.

Steps to Reproduce

1. Create a project with 10up-toolkit@6.5.1 as the only dev dependency (no explicit webpack pin).
2. Run npm install — npm resolves webpack to 5.106.2.
3. Run npm run build.

Error Output

ValidationError: Invalid options object. Progress Plugin has been initialized
using an options object that does not match the API schema.

options should be one of these: object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? } | function Details:
options has an unknown property 'name'.
options has an unknown property 'color'.
options has an unknown property 'reporters'.
options has an unknown property 'reporter'.

Full stack trace points to 10up-toolkit/scripts/build.js:30.

Root Cause

webpack 5.106.2 removed the name, color, reporters, and reporter
properties from the ProgressPlugin options schema. 10up-toolkit's build
script passes an options object containing those properties, which now fails
schema validation.

Workaround

Pin webpack to 5.105.2 via npm overrides in package.json:

"overrides": {
  "webpack": "5.105.2"
}

Then reinstall:

rm -rf node_modules package-lock.json && npm install

Expected Behaviour

npm run build should work with the webpack version npm resolves automatically, without requiring a manual override.

Screenshots, screen recording, code snippet

No response

Environment information

• 10up-toolkit: 6.5.1
• webpack (broken): 5.106.2
• webpack (working): 5.105.2
• Node.js: v24.14.0
• npm: 10.x
• Device: MacBook Pro
• OS: Tahoee 26.4.1

WordPress information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[benlk]

Verified that the workaround works.