Build failing after webpack upgraded to `v5.106.0` at Apr 8, 2026, 8:41 PM GMT+5:30

[vaibhav-khedekar-webuy]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Prerequisites

• I'm using the latest version of Docusaurus.
• I have tried the npm run clear or yarn clear command.
• I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
• I have tried creating a repro with https://new.docusaurus.io.
• I have read the console error message carefully (if applicable).

Description

Removed deprecated functionality in current release v5.106.0
which might affect Docusaurus build failed.

Reproducible demo

No response

Steps to reproduce

• update to latest docusaurus version
• try to build

Expected behavior

Build gets fail.

Actual behavior

ERROR] Error: Unable to build website for locale en.
at tryToBuildLocale (/app/site/node_modules/@docusaurus/core/lib/commands/build/build.js:76:15)
at async /app/site/node_modules/@docusaurus/core/lib/commands/build/build.js:34:9
... 4 lines matching cause stack trace ...
at async file:///app/site/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 {
#13 259.4 [cause]: ValidationError: Invalid options object. Progress Plugin has been initialized using an options object that does not match the API schema.
#13 259.4 - options should be one of these:
object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? } | function
Details:

• options has an unknown property 'name'. These properties are valid:
  object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? }
  -> Options object for the ProgressPlugin.
• options has an unknown property 'color'. These properties are valid:
  object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? }
  -> Options object for the ProgressPlugin.
• options has an unknown property 'reporters'. These properties are valid:
  object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? }
  -> Options object for the ProgressPlugin.
• options has an unknown property 'reporter'. These properties are valid:
  object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? }
  -> Options object for the ProgressPlugin.

Your environment

• Public source code:
• Public site URL:
• Docusaurus version used:
• Environment name and version (e.g. Chrome 89, Node.js 16.4):
• Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

• I'd be willing to fix this bug myself.

[slorber]

Can you please share a repro?

I can't help without a repro because it's unclear if you are using Docusaurus Faster, and what's in your lockfile, among other things.

I just upgraded our monorepo to that specific version, and it works fine for us and our init template: #11924

Eventually, try to upgrade related transitive dependencies, such as this one: https://github.com/unjs/webpackbar

[slorber]

Hmmm, it seems to work with webpackbar v7 but not v6 (used by Docusaurus v3.10)

Will need to investigate

@alexander-akait, any idea what could be the cause?

[carry0987]

Same error here

[vaibhav-khedekar-webuy]

@slorber Recent versions of Webpack (5.106.0) enforce strict schema validation for ProgressPlugin.
Some internal dependencies (e.g., webpackbar or indirect plugins) still pass deprecated/unsupported options like name, color, and reporter, causing the build to fail.

[slorber]

Thanks

I think we should be able to update to webpackbar v7 in a patch release; it shouldn't be a Docusaurus v3 breaking change. Until v3.10.1 gets released, pin an older version of webpack, and it should be fine (use npm overrides or yarn resolutions)

[vaibhav-khedekar-webuy]

@slorber Yes, we have already did it in our project, created this issue to aware all.

"overrides": {
    "webpack": "5.105.4"
  },

This webpack version works fine, tested!

[alexander-akait]

@slorber If it's critical, I can temporarily remove validation and release a patch, but honestly, validation is a good thing for such cases, we also have strict typescript types to prevent this...

[slorber]

Thanks @alexander-akait , I think we may not need it.

@vaibhav-khedekar-webuy and others, could you try the opposite, upgrade Webpack, but instead override webpackbar?

NPM:

"overrides": {
    "webpackbar": "^7.0.0"
},

Yarn:

"resolutions": {
    "webpackbar": "^7.0.0"
},

If this works, then we could easily release a patch doing this upgrade in v3.10.1

Are you all able to upgrade to v3.10, or is there any blocker? (normally our minor versions do not have breaking changes so it should be easy)

[markscott-ms]

I have also encountered this issue with v3.10.0 and doing a site build.

Adding (only) the override of webpackbar to ^7.0.0, as suggested by @slorber, made the build successful.

[vashek]

I also confirm the 7.0.0 override fixes the build.

[carry0987]

So right now we just need to wait for version 3.10.1 release?