Nico Jansen

You might want to go all-the-way and migrate this library itself to esm.

I've just tried it but there still seems to be a hanging elektron process after killing karma with ctrl+c.  ```bash nicoj@NicoJ02 MINGW64 /c/z/github/nicojs/stryker-miniq-demo (master) $ npm ls karma-nightmare [email protected]...

Does anyone know how to do calls? One of the interfaces generated seems to be for a soap client. For example the `ITempConvertSoap12Soap` interface (with the https://www.w3schools.com/xml/tempconvert.asmx?WSDL example)

Currently jest config as TS is not supported (I didn't know it was a feature). Could you try migrating to JS? Alternatively you can comfigure `ts-node` using `testRunnerNodeArgs` in stryker.conf.json

https://jestjs.io/docs/configuration

Note: we are working on getting this functionality exported from `jest-config` so we can support it out-of-the-box.

Hi @HonzaMac thanks for opening this issue. I think `stryker init` should provide the `-W` flag in this case. As a workaround, you can use `yarn add --dev -W @stryker-mutator/core`....

What is your node version? And does this command work? `yarn run stryker run`

This is all very strange to me! > Seems it ignores proxy settings. This shouldn't be the case. We use [`typed-rest-client`]( https://github.com/Microsoft/typed-rest-client#readme), which supports these env variables: https://github.com/microsoft/typed-rest-client/blob/master/lib/HttpClient.ts#L96-L100 ```typescript enum...

True. What do you suggest to improve this? Can we add `-W` in all our docs? Or add to the troubleshooting page?