repro: type-checking issue with script setup in v2.0.1 #1601
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for vue-test-utils-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
cexbrayat
force-pushed
the
repro/typechecking-issue-in-v2.0.1
branch
from
bbe73c4
to
42dd013
Compare
cexbrayat
changed the title
|
@pikax Did you had time to take another look at this? It would be great to unblock and cut another release with the fix. No worries if you haven't, I just wanted to make sure it's still on your radar 😉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There is a type-checking issue with VTU v2.0.1 (not with v2.0.0) when using the latest vue-tsc and components with script setup. This is reproducible in the repo if we bump t the latest vue-tsc (which necessitates to work around vuejs/language-tools#1452).
We should fix and release, as people using TS and script setup will most likely encounter the issue.