Nico Jansen

@babilog do you have the tests? I would be grateful for them 🥇

Shouldn't the option be renamed to `changeHost`? We actually need the use case of changing the origin header. How to contribute if the name is already taken? 😕

How would you want the type `Mocha.Rc` to be kept in sync with the json schema? I have some experience with this using https://github.com/bcherny/json-schema-to-typescript. Do you want me do create...

I would also suggest to use the schema for validation, but that would be a different PR I think.

Let me do a proposal. I want to create and maintain a good package that provides you with the most accurate location of the call site. I've already started it...

I'm pretty sure this effect is by design. It is explained here: https://mochajs.org/#parallel-mode. Since tests are executed in parallel processes (note: processes _not worker threads_), they are only reported back...

No there isn't at the moment. Each test runner worker process reports back only once at the end, so you'll always see them buffered. The only workaround I can currently...

@saschanaz I think you are correct that this should be fixed with #7208 by setting `html-whitespace-sensitivity` to `strict`. However, there is no way for us to verify that (playground doesn't...

I've found a workaround: ```js class ErrorWithCallSite extends Error { constructor(from: (...args: any) => any) { super(); Error.captureStackTrace(this, from); } public static prepareStackTrace(err, stack:) { return stack; } } function...

Thanks for your extensive reply! Interesting stuff. > As far as I know there's no portable API to get a machine-readable stack trace. Yeah, no way around parsing the stack...