You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since updating to 0.40.0 (and later 0.40.1), we are unable to use vue-tsc on our project. On that version, we get errors like these on pretty much all of our Vue SFCs:
...
src/[...].vue - error TS6133: '...' is declared but its value is never read.
...
We are using Vue 3 and SFCs with setup scripts all throughout our application.
Reading other issues that reported similar issues, it looks like they were either using Vue 2 or had their issue fixed by editing their tsconfig.json. However, we use Vue 3 and our tsconfig.json includes these lines:
Our project was ported from using vue-cli and we didn't consider type-checking in templates at the time, which is why we need experimentalDisableTemplateSupport enabled. Disabling it gets rid of these errors, but introduces hundreds of other ones. Also, the IDE (WebStorm) some of us use didn't support Typescript syntax inside templates at the time.
The text was updated successfully, but these errors were encountered:
Hello
Since updating to 0.40.0 (and later 0.40.1), we are unable to use vue-tsc on our project. On that version, we get errors like these on pretty much all of our Vue SFCs:
We are using Vue 3 and SFCs with setup scripts all throughout our application.
Reading other issues that reported similar issues, it looks like they were either using Vue 2 or had their issue fixed by editing their
tsconfig.json
. However, we use Vue 3 and ourtsconfig.json
includes these lines:Our project was ported from using
vue-cli
and we didn't consider type-checking in templates at the time, which is why we needexperimentalDisableTemplateSupport
enabled. Disabling it gets rid of these errors, but introduces hundreds of other ones. Also, the IDE (WebStorm) some of us use didn't support Typescript syntax inside templates at the time.The text was updated successfully, but these errors were encountered: