-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrading vue-tsc
from 2.0.29 to 2.1.x results in hundreds of TypeScript errors
#128
Comments
I cloned
|
@ruojianll: I cannot reproduce this issue with vue-tsc 2.1.0, however I face this issue with 2.1.2. It seems that vue-tsc 2.1.2 cannot infer the components types. Please see: vuejs/language-tools#4747 @basil : Are you sure that you didn't installed vue-tsc 2.1.2?, can you check you package-lock.json? |
It's possible, vite-plugin-vue also removed decorator support in .vue file. Use some temporary resolutions such as ts |
The CI build failed: https://github.com/neanes/neanes/pull/933/checks I wonder if |
Checking the |
Hi @ruojianll, I saw that the related PR vuejs/language-tools#4763 was released in 2.1.4. As you can see from the CI build for neanes/neanes#936, this does not resolve the issue and I still get 283 new TypeScript errors with |
I cannot reproduce this with vue-tsc 2.1.0, but can with 2.1.2. Node v20.17.0 Errors look like (I'm mentioning this in the hope of Google picking it up, as Googling the error didn't work for me) |
vue-tsc
from 2.0.29 to 2.1.0 results in hundreds of TypeScript errorsvue-tsc
from 2.0.29 to 2.1.x results in hundreds of TypeScript errors
Upgrading
vue-tsc
and@vue/language-core
from 2.0.29 to 2.1.0 (and nothing else) results in 283 new TypeScript errors for me. To reproduce, check out neanes/neanes#933 and runnpm install && npm run build
. The default branch builds correctly. This issue was originally reported at vuejs/language-tools#4748, where @davidmatter wrote thatThe text was updated successfully, but these errors were encountered: