Yaroslav Admin

Sounds good to me!

I would say it is a bug in Karma, which we should fix. This will be a breaking change though. What happens is that Karma resolves the relative `basePath` relative...

Note that this can not be done before IE 9-10 support is dropped as Mocha is used for [client-side tests](https://github.com/karma-runner/karma/blob/master/test/client/karma.conf.js#L123) and any newer version does not work in IE 9-10...

> seems Node 10 doesn't have matchAll. Easy to replace. I'll update it when I get time. I would be more comfortable landing this change in a major release, so...

Depending on what you're trying to achieve, maybe http://karma-runner.github.io/6.3/config/configuration-file.html#browserdisconnecttolerance will work? > Only question that remains is: is this a stable API? I guess time will tell... 😅? He-he, indeed!...

> There currently is no way to recover from this. The browser isn't restarted or closed and there is no way to force this in the karma API. The only...

> Is that future proof-ish? 😅 Yes, I would say so! > Would there still be a possibility to start a new one automatically? Or will that be the default...

@johnjbarton Good idea! We can both retain strict validation of Karma options and allow users to pass arbitrary custom options. The only concern is that we already use this feature...

So I think the best solution would be to introduce `--client-args` flag for `karma run` command, then add a warning that the behavior of `karma run -- my-arg` form is...

@paulie4 Thanks for sharing! Looking at this library I start to think that maybe we should provide an API for a plugin to register their CLI arguments. This way there...