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
TLDR: massive amount of vague/cryptic errors occur in the default initial project from npm create vue@latest in a basically vanilla vue & typescript environment.
I'm confused about the change of addons for VScode. It says in the changelog that Volar is deprecated, so I disabled it.
VScode is up to date at 1.87, and so is the "Vue - Official" addon at 2.0.4. No additional preferences pertaining to vue have been changed from their defaults.
I'm getting these weird errors in a super simple component:
Needless to say, this runs free of errors/warnings during compilation and at runtime. These errors are ONLY shown in VScode and nowhere else. What are they trying to tell me?
Worthy of note: this component has been put in the example app created by npm create vue@latest about two weeks ago. So to reproduce the problem, use that command. I just tried it myself, and the errors occur straight away after setting up the default/initial/example project using that command. Only options chosen: typescript and eslint. All other options were left default.
The text was updated successfully, but these errors were encountered:
TLDR: massive amount of vague/cryptic errors occur in the default initial project from
npm create vue@latest
in a basically vanilla vue & typescript environment.I'm confused about the change of addons for VScode. It says in the changelog that Volar is deprecated, so I disabled it.
VScode is up to date at 1.87, and so is the "Vue - Official" addon at 2.0.4. No additional preferences pertaining to vue have been changed from their defaults.
I'm getting these weird errors in a super simple component:
The component:
Needless to say, this runs free of errors/warnings during compilation and at runtime. These errors are ONLY shown in VScode and nowhere else. What are they trying to tell me?
Worthy of note: this component has been put in the example app created by
npm create vue@latest
about two weeks ago. So to reproduce the problem, use that command. I just tried it myself, and the errors occur straight away after setting up the default/initial/example project using that command. Only options chosen: typescript and eslint. All other options were left default.The text was updated successfully, but these errors were encountered: