Update fork-ts-checker-webpack-plugin to the latest version 🚀 #35
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.
The devDependency fork-ts-checker-webpack-plugin was updated from
0.5.2to1.0.0.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Release Notes for v1.0.0
This is the first major version of
fork-ts-checker-webpack-plugin. A long time coming :-)There are actually no breaking changes that we're aware of; users of 0.x
fork-ts-checker-webpack-pluginshould be be able to upgrade without any drama. Users of TypeScript 3+ may notice a performance improvement as by default the plugin now uses the incremental watch API in TypeScript. Should this prove problematic you can opt out of using it by supplyinguseTypescriptIncrementalApi: false.We are aware of an issue with Vue and the incremental API. We hope it will be fixed soon - a generous member of the community is taking a look. In the meantime, we will not default to using the incremental watch API when in Vue mode.
The plugin supports webpack 2, 3, 4 and 5 alpha and TypeScript 2.1+ alongside tslint 4+.
See also: https://blog.johnnyreilly.com/2019/03/the-big-one-point-oh.html
Commits
The new version differs by 15 commits.
2c03b7eprepare for 1.0 release (#218)2dad936fixuseTypescriptIncrementalApiflag to work according to docs (#223)547d087default to incremental api usage to true if TS 3+ (#217)03c612eRespect tslint configs hierarchical order (#214)903d1deignoreLintWarnings option (#213)8c339d3Format code samples (#215)f0457ddensure we don't depend directly on typescript (#208)7d762cbmake tests run cross platform (#206)2ccecefmore unit tests (#205)4537c16typescript path can now be specified (#204)bb8dbf8make node 6 compatible (#202)e66e912replace peerDeps with runtime checks (#201)3a312eaAdd incremental compilation. (#198)51981e7refactor(object-spread): use spread instead of assign (#194)683ed7a[WIP] webpack@5hookssupport (#166)See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴