Error: No browsers were started. Browser launcher configuration

Goal

To execute a test suite across multiple browsers using Karma, but the run aborts with the message "No browsers were started. Did you forget to install the browser launcher?" when a referenced launcher is missing.

Constraints & Uncertainty

Karma validates the browsers array against installed launcher plugins (e.g., karma-chrome-launcher). The current implementation merely reports the error and exits; it does not attempt to auto‑install missing binaries. When multiple browsers are listed, the presence of a single missing launcher aborts the entire run, even if other launchers are available.

Unresolved Decision

It is unclear whether Karma should provide an automatic fallback to download or install the required browser binary when a launcher is referenced but not installed, and how to configure selective failure for individual launchers.

Questions

• Should Karma attempt to auto‑install missing browser binaries when a launcher is referenced but not present?
• How can Karma be configured to ignore a missing launcher and continue with the remaining available browsers?
• Is there a flag or setting that controls whether a single missing launcher aborts the entire run or only the specific browser?