Maks Rafalko

I would like @infection/core to participate here, as you are touching a very complex topics. My 2 cents, to have something to look at for myself in the future: Questions...

Hey, could you please try to install Infection locally as a composer dependency (or as a global package) to be able to update the source code and try to pass...

There was a [WIP PR](https://github.com/infection/infection/issues/1578) back in 2021, but nobody has tried to finish it since then. Help is welcome :) @sivlev @vudaltsov what are your use-cases? Just for understanding....

> [@maks-rafalko](https://github.com/maks-rafalko), if you like this "hack", I will be happy to work on the PR. absolutely! Comparing to other things we do here in Infection (e.g. [here](https://github.com/infection/include-interceptor)) it's not...

> sounds like it might make sense to ignore some errors via [phpstan-identifier via phpstan config](https://phpstan.org/blog/phpstan-1-11-errors-identifiers-phpstan-pro-reboot). idea here was not to run PHPStan at all (in this particular case), because...

I will experiment with your idea and keep this PR on hold

@jongomes did you find a solution to this problem? Does `eager: true` help?

Though it would be nice to have `.writeEnvironmentInfo({...})` public API for Jest, as currently we write there dynamic data, not only data from jest config. In referenced PR I see...

up We are upgrading to v3 and we still can't dynamically write environment info. Please consider to somehow allow providing dynamic values. Our use case - we test N microservices...

> My gut feeling is we maybe can speedup the overall process by not using a worker, but run the analysis in the main process per mutation to reduce process...