chore(deps): update @stryker-mutator/core -> 5 - devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@stryker-mutator/core (source)	^4.5.1 -> ^5.0.1

---

Release Notes

stryker-mutator/stryker-js

v5.0.1

Compare Source

Bug Fixes

• jest-runner: Support Jest v27 (#​2861) (8d3560b)
• mocha-runner: improve debug logging (#​2925) (ecc53ee)

v5.0.0

Compare Source

Bug Fixes

• sandbox: make directory if not exists before symlinking node_modules (#​2856) (40f9a1d)
• vue-tsx: support parsing tsx script in .vue file (#​2850) (dc66c28)

Features

• es: convert to es2019 (#​2846) (36c687f)
• ignore patterns: add "ignorePatterns" config option (#​2848) (a69992c), closes #​1593 #​2739
• jest: report test files and test positions (#​2808) (c19095e)
• jest-runner: drop projectType "create-react-app-ts" (#​2788) (2581e32), closes #​2787 #​2787
• mutators: mutate nullish coalescing operator (#​2884) (021a419)
• node: Drop support for node 10 (#​2879) (dd29f88)
• options: make "perTest" the default for "coverageAnalysis" (#​2881) (518ebe6)
• range: remove Range from the API (#​2882) (b578b22), closes #​322
• report: add test details and metadata to JSON report (#​2755) (acb0a3a)
• report: report test states (#​2868) (e84aa88)
• reporter api: unify reporter api with mutation-testing-elements (#​2798) (d173b27), closes #​2766
• serialize: remove surrial (#​2877) (5114835)

BREAKING CHANGES

• range: The range property is no longer present on a mutant. Note, this is a breaking change for plugin creators only.
• options: "perTest" is now the default value for "coverageAnalysis" when the configured test runner is not "command". Explicitly set "coverageAnalysis": "off" manually to opt-out of this behavior.
• node: Node 10 is no longer supported. Please use Node 12 or higher.
• serialize: Having a non-JSON-serializable value in your configuration won't be sent to the child process anymore. If you really need them in your test runner configuration, you should isolate those values and put them in test runner-specific config files, loaded by the test runner plugin itself, for example, jest.config.js, karma.conf.js, webpack.config.js.
• ignore patterns: Stryker will no longer use a git command to determine which files belong to your project. Instead, it will rely on sane defaults. You can change this behavior by defining ignorePatterns.
• ignore patterns: The files configuration option is deprecated and will be removed in a future release. Please use ignorePatterns instead.

This:

{
  "files": ["foo.js"]
}

Is equivalent to:

{
  "ignorePatterns": ["**", "!foo.js"]
}

• reporter api: Changes to Reporter and TestRunner plugin API of Stryker
• jest-runner: Support for project type create-react-app-ts is dropped from the jest-runner.

v4.6.0

Compare Source

Features

• mutation range: allow specifying a mutation range (#​2751) (84647cf)
• rename: rename to StrykerJS (#​2813) (dc08592), closes #​2754

4.5.1 (2021-03-11)

Bug Fixes

• babel-transformer: respect top of the file comments/pragma (#​2783) (ca42276)
• instrumenter: corect mutant location in .vue and .html files (547a25c), closes #​2790
• peer-deps: use correct peer dep version (a6ca0f2)

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[brodybits]

I think we should test this before merging, would also like it if we could switch to the Jest runner as I started working on in PR #208.

[karfau]

Just started it on my machine and it works in it's current state.
I think we should rather update #208 to take care of switching to jest runner, so I would say we land this one.

[brodybits]

I think we should rather update #208 to take care of switching to jest runner, so I would say we land this one.

I guess you mean land this one first and then update the changes for the Jest runner (from PR #208) to work with Stryker JS 5. This is the approach that I would take.

I would be a bit curious, though, if we can measure the difference in performance between Stryker 4.5.1 and 5.0.1. I did this before with 2 vCPU cores, which seemed to be the most consistent with GitHub.

I do find it pretty unfortunate that the Stryker run takes so long on GitHub.