Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ fork-ts-checker-webpack-plugin (5.2.0 → 6.0.3) · Repo · Changelog
Release Notes
6.0.3
6.0.2
6.0.1
6.0.0
5.2.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
fix: use cwd in async: false mode for consistency (#533)
fix: avoid recursive rebuilds on webpack 5 (#532)
fix: remove .ts extension for .vue files in dependencies (#528)
Merge pull request #526 from TypeStrong/alpha
Merge branch 'master' of github.com:TypeStrong/fork-ts-checker-webpack-plugin into alpha
fix: file path for webpack base on process.cwd (#524)
feat: add support for "generateTrace" tsconfig option (#523)
Merge pull request #522 from TypeStrong/update-alpha
Merge branch 'master' of github.com:TypeStrong/fork-ts-checker-webpack-plugin into update-alpha
chore: speed up e2e tests by adding a few caching layers
chore(deps): bump npm-user-validate from 1.0.0 to 1.0.1 (#519)
chore: add retry for e2e tests to improve dx (#520)
feat: use webpack's built-in watching instead of polling
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands