run.target: ["chromium"] ignored in config

[fregante]

Is this a feature request or a bug?

bug

What is the current behavior?

A plain $ web-ext run will read/validate webExt.run.target from my package.json, but then it ignores it.

// package.json
{
  "webExt": {
    "run": {
      "target": ["chromium"]
    }
  }
}

This verbose log line explains why: the CLI parser is providing its own defaults before merging with the config file.

[web-ext/lib/config.js][debug] Favoring CLI: target=firefox-desktop over configuration: target=chromium

What is the expected or desired behavior?

The config file should be respected by applying the defaults after reading the config file.

Version information (for bug reports)

• Your OS and version: macOS 15.1.1

node --version && npm --version && web-ext --version
v23.1.0
10.9.0
8.3.0

[Rob--W]

This message is emitted from

web-ext/src/config.js

Lines 121 to 124 in 958e1d4

	log.debug(
	`Favoring CLI: ${option}=${argvFromCLI[option]} over ` +
	`configuration: ${option}=${configObject[option]}`,
	);

. We probably have a bug there that we should fix.

[fregante]

the CLI parser is providing its own defaults before merging with the config file.

Likely here:

web-ext/src/program.js

Line 583 in 64ad32f

default: 'firefox-desktop',

Yargs is passing the default the same way it would pass a user-provided flag, therefore overriding any config that is found later.

I'd review other such defaults in the file. If they're all ignored the same way, they should probably all be removed.

Yargs' own docs/bugtracker probably detail how to deal with configuration vs flag overrides.