Bump fork-ts-checker-webpack-plugin and notifier, update from babel-eslint to babel/eslint-parser #1985
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following #1983, a typeerror began emanating from the
fork-ts-checker-webpack-plugin
package during builds, due to the bump in the version of eslint. Whilst builds were still successfully producing artefacts, it's possible we'd no longer be notified of ts issues.This updates
fork-ts-checker-webpack-plugin
to version 6.5.3.. version 7.0.0 and onward drop support for webpack 4 and eslint, which would require a much larger change. Also updated is thefork-ts-checker-notifier-webpack-plugin
package to version 4.0.0.The update to
fork-ts-checker-webpack-plugin
necessitated an upgrade frombabel-eslint
to@babel/eslint-parser
due to an error emanating from eslint-scope during builds. The only necessary change from this was to update our eslint config to use@babel/eslint-parser
instead.