Bumped the peer dependency range for
vue-tscto^2.1.0because there was a breaking change in its API. If you're using Vue support, upgrade both packages simultaneously, e.g.npm i -D prettier-plugin-organize-imports vue-tsc.
Does any of this look wrong? Please let us know.
See the full diff on Github. The new version differs by 14 commits:
4.2.0chore:
update all dev dependenciesfix:
use `getDefaultCompilerOptions` from vue-tsc instead of the deprecated
`resolveVueCompilerOptions`feat:
allow vue-tsc 3 as peer dependencychore(ci):
remove `check-types` step (part of `test` now)4.1.0chore:
update dev dependenciesdocs:
update changelogfeat:
support vue-tsc v2.1 (#136)chore(ci):
run on node 22chore(ci):
fix run-script invocationchore:
use tsc to type-check the projectchore(tests):
upgrade ava from v3 to v6fix:
drop `@vue/language-plugin-pug` as peer dependency
- @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 cancel merge
- Cancels automatic merging of this PR
- @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)