When I run npm run watch, this is what I get.

[webpack-cli] 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'. 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.

Comments

xamalu.xyoks@gmail.com created an issue. See original summary.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Assigned: xamalu.xyoks@gmail.com » Unassigned
dokuf’s picture

dokuf commented

Same here, tried it on different environments - local, in docker container, DDEV always the same problem

Why does this issue have minor priority if it blocks installation/usage completely?

After some help of AI I removed webpackbar and now it works.

paulmckibben’s picture

paulmckibben
he/him
Primary language English
Location Atlanta, GA
commented
Category: Support request » Bug report
Priority: Minor » Normal

I also ran into this upon creation of a new radix subtheme. Bumping priority to "normal" and changing category to "bug report". I suspect something has gone awry with dependencies.

paulmckibben’s picture

paulmckibben
he/him
Primary language English
Location Atlanta, GA
commented

I was able to work around the problem by downgrading Webpack to a version that doesn't enforce strict schema validation.

I added the following to my subtheme's package.json file (between the "scripts" section and the "devDependencies" section):

	"overrides": {
		"webpack": "~5.74.0"
	},

I then removed package.lock and did npm install again.

After that, I was able to npm run watch and npm run production without any issue.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
f0ns’s picture

f0ns commented

Also ran into the issue, the fix in #5 worked for me.

chrisck’s picture

chrisck
he/him
Location BC, Canada
commented

Thanks @paulmckibben. #5 worked for me too.

  • doxigo committed 3ec388bb on 6.0.x 
    Issue #3584633: Pin webpack to 5.89.0 in starterkit to fix laravel-mix...
doxigo’s picture

doxigo commented
Version: 6.0.2 » 6.0.x-dev
Status: Active » Fixed

temporarily fixed it this way, now we are pinned on a 2 year old webpack release. we need to migrate to Vite soon given laravel-mix is really dead. Thanks everyone

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.