Update @stryker-mutator/core -> ^4.5.1 - devDependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@stryker-mutator/core	^4.4.1 -> ^4.5.1

---

Release Notes

stryker-mutator/stryker

v4.5.1

Compare Source

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)

v4.5.0

Compare Source

Bug Fixes

• logging: log info about symlinking on debug (#​2756) (c672e2e)
• mutator: don't mutate string literal object methods (#​2718) (964537a)
• reporting: report test name when a hook fails (#​2757) (5e062b2)
• typescript-checker: improve error reporting (2502eba)
• typescript-checker: resolve tsconfig files correctly (8cf9e8c)

Features

• package: restructure package internals (#​2714) (e1711d2)
• sandbox: support symlinking of node_modules anywhere (ee66623)

4.4.1 (2021-01-27)

Bug Fixes

• jest-runner: support custom rootDir (312f6fe)

---

Renovate 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]

@karfau can you check this update?

[karfau]

@brodybits what specifically should I check?
(I already know that the new tests added as part of the security fix break the stryker setup, since they rely on line numbers in snapshots, and stryker mutates the files causing line numbers to change.)
My capacity is quite low right now...

[brodybits]

I have taken assignment of issue #200 that I just raised to deal with the Stryker test failures, and I have taken assignment of this PR for now. Since the Stryker test is not run on each PR, one of us needs to check that this Stryker update will work correctly before merging.

In case another maintainer wants to take this over and try running this update before merging, I would be grateful.

[brodybits]

I will try running Stryker with this update now and merge if it looks OK.

[brodybits]

Results are almost the same, merging.