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
Type checking ignores script-setup blocks #6716
Comments
@sodatea This issue and #6736 are related to But think a little further, is it better to create Vue3 project with vue-cli-plugin-vite? Vite can provide long-term support for Vue3. |
I noticed this problem too and saw your issue in |
Using We are currently using vite in the So what I suggest is that users should install this |
@screetBloom Thanks for reply. That's what I've been wondering about lately: the current role of vite and vue-cli. Based on some understanding of your answer, although vite's build mode relies on rollup, but there still a cost of migrating from webpack to rollup in real-world projects.
|
any progress on this? |
Please update to https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/releases/tag/v6.4.1 where the issue is fixed. |
There still seems to be some problems, I will comment under the #676 |
Ok, then this issue can be closed |
No. While it worked for me, others are still reporting uncovered edge cases. |
it worked for me too, then it can be closed first, for unknown case maybe can add another issue |
Hi! Sorry to reopen, I have this problem with Vue 3 and script setup not showing typescript errors on console. I tried forcing fork-ts-checker version with pnpm but no changes. Did you manage to resolve it? |
The first try to solve this in fork-ts-checker-webpack-plugin was reverted and no further attempt has been made afaict. |
Thanks @bodograumann ! Decided to use |
Version
5.0.0-beta.4
Reproduction link
github.com
Environment info
Steps to reproduce
Add some wrongly typed code. E.g.:
Build
What is expected?
The typescript error is detected and the build fails.
What is actually happening?
The typing is simply stripped and no error can be seen.
The text was updated successfully, but these errors were encountered: