Linting error EXTENSION_ID_REQUIRED for v3 extension targeted towards Chromium

[Connum]

Is this a feature request or a bug?

Bug

What is the current behavior?

When linting an extension using a v3 manifest, it shows the error EXTENSION_ID_REQUIRED for the manifest.json. That's ok for Firefox, so I can get rid of it by adding

  "browser_specific_settings": {
    "gecko": {
      "id": "[email protected]"
    }
  }

but then, Chrome will show an error upon installation stating that "browser_specific_settings" is an unsupported key. (The extension will be installed and activated, but still, it will show that error on the extensions page.)

I thought I could maybe use the following:

  "web_accessible_resources": [{
    "resources": [],
    "matches": [],
    "extension_ids": ["[email protected]"]
  }]

but that will not get rid of the error.

What is the expected or desired behavior?

Either provide an argument to disable the error when targeting Chromium, or support an extension id syntax that works for both Chromium and Gecko environments.

Version information (for bug reports)

• Firefox version: not applicable, as targeting Chromium - Chrome version: 127.0.6533.89
• Your OS and version: Windows 10
• Paste the output of these commands:

node --version && npm --version && web-ext --version

v18.15.0
8.15.0
8.2.0

[Rob--W]

The warning in Chrome is not fatal, there is a feature request at https://issues.chromium.org/issues/40196501 to stop emitting errors for known keys.