@Rob--W -- thanks for the review and the link to the issue, I hadn't realised that this is a known issue. Without --test-type, the message shown by Chromium is rather annoying. I also discovered in my testing that the --remote-debugging-port option does not exhibit the above issue, so a potential solution could be to switch to that instead. Before I start looking into that, are there any reasons you can think of why this solution wouldn't work or wouldn't be desired?

@Rob--W -- thanks for the review and the link to the issue, I hadn't realised that this is a known issue. Without --test-type, the message shown by Chromium is rather annoying.

Even without --test-type set by default, you can start web-ext run with --args=--test-type (or its shorthand) if you'd like.

I also discovered in my testing that the --remote-debugging-port option does not exhibit the above issue, so a potential solution could be to switch to that instead. Before I start looking into that, are there any reasons you can think of why this solution wouldn't work or wouldn't be desired?

The --remote-debugging-port option does not allow loading of extensions, see #3388.

For this and other alternatives that I considered, see #3388 (comment)

@Rob--W -- I removed the --test-type flag and added logic to avoid passing --disable-blink-features=AutomationControlled when --enable-blink-features is set with AutomationControlled. I think the right place to mention --test-type would be in the documentation, though I couldn't find the source for that.

Not sure why the dependency audit is failing, I didn't change any dependencies.

@Rob--W -- Thanks for the suggestions, I've committed those now.