chore(deps): update dependency fork-ts-checker-webpack-plugin to v4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
fork-ts-checker-webpack-plugin	dependencies	major	^3.1.1 -> ^4.1.2

---

Release Notes

TypeStrong/fork-ts-checker-webpack-plugin

v4.1.2

Compare Source

Bug Fixes

• fix "ESLint fix option silently fails" issue (#​401) (5be63fa), closes #​400

v4.1.1

Compare Source

Bug Fixes

• add a warning message for SIGINT (4013a3f)

v4.1.0

Compare Source

Features

• Support ESLint fix option (54a51c7), closes #​323

v4.0.5

Compare Source

Bug Fixes

• properly output chained Typescript errors (#​390) (d083fc8)

v4.0.4

Compare Source

Bug Fixes

• prevent null-pointer error after killing child process (642b5bf), closes #​363

v4.0.3

Compare Source

Bug Fixes

• change import of crypto (1c82006)

v4.0.2

Compare Source

Bug Fixes

• remove @​types/eslint dependency as eslint is optional (a9db0d0), closes #​379

v4.0.1

Compare Source

Bug Fixes

• bump patch version because of previous misconfiguration (27f2719)

---

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.

[kevinmarrec]

@rchl @danielroe @NickBolles any help is appreciated if you guys know how to migrate to the new webpack plugin version. It seems some options of the plugin OR that the signature of the plugin itself have changed and just make the thing broken when trying to upgrade ^^

[NickBolles]

@kevinmarrec or whoever looks at this next. I took a few minutes to look at this. I'm not too sure whats going on. here's some info though:
webpack package versions:

 ~> yarn list --pattern *webpack*
yarn list v1.22.4
├─ @nuxt/[email protected]
├─ @nuxt/[email protected]
│  └─ @types/[email protected]
├─ @nuxt/[email protected]
├─ @types/[email protected]
├─ @types/[email protected]
├─ @types/[email protected]
├─ @types/[email protected]
├─ @types/[email protected]
├─ @types/[email protected]
├─ @types/[email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
│  └─ [email protected]
└─ [email protected]

I don't see anything that would obviously cause this from thee fork-ts-checker-webpack-plugin 4.0 release notes

[rchl]

It seems to do with how the new version of fork-ts-checker-webpack-plugin is compiled. Previously it targeted es6 and code was compiled into classes where methods pass the instanceof Function check while currently it's compiling to es5 target and methods are added through prototype chain and no longer pass instanceof Function check.

This problem only manifests itself when combined with jest mocking the function (bug jestjs/jest#6329 which is a duplicate of unsolved one).

[rchl]

Created PR #322 with a fix.

[NickBolles]

@rchl woah. Gnarly one! Nice job!