Honza Machala

Could you provide more info which steps do you do manually?

Cc @naugtur ?

We have currently have test-case which check those "satisfies" from instrument code. It would be great to expose "satisfies" from each instrumentation. We need these checks because of Renovate Bot...

I would probably prefer more special function: ```js const commonPackageJson = require('./../../common/package.json'); const apm = require('elastic-apm-node') console.log(apm.isSupported(commonPackageJson['dependencies']['pg']) ``` In this case, I don't need to have dependency on my side...

We need to add: - [x] Support for 0.95 - added in #2740 - [ ] Support for 1.x - added in #3046 - [ ] Support for 2.x

Try `pm2 logs pm2-logrotate` and you will see, what is wrong. Which node version are you using?

Problem is, that you have newer version of logrotate, that does not support old node 4.x Last working is `2.2.4`, downgrade. `pm2 install [email protected]`

I've run `yarn add --dev -W @stryker-mutator/core` manually and proceed with `stryker init --fileLogLevel trace` once more. I've received this error: ``` ➜ web git:(feature/stryker-common-package) ✗ stryker init --fileLogLevel trace...

node: v16.15.1 > `yarn run stryker run` It has exactly same output. ``` import pkg from 'execa'; const { execaCommand } = pkg; ``` If I modify code directly, it...

And after this I receive another issue. Seems it ignores proxy settings. ``` ➜ web git:(feature/stryker-common-package) ✗ stryker init --fileLogLevel trace ? Are you using one of these frameworks? Then...