Johnson Chu

VSCode's TS client does not provide a configuration method for `extraFileExtensions`, so this is currently not configurable in VSCode for Vue. https://github.com/microsoft/vscode/blob/8aca9a53311890fa54f0459c6ef2e8994d4d8ae4/extensions/typescript-language-features/src/languageFeatures/fileConfigurationManager.ts#L128-L129

This problem cannot be solved on our side, but 2.0.7 has re-introduced the v1 language server, you can upgrade and make sure not to enable Hybird Mode to get consistent...

I am currently unable to find time to investigate it, but let's keep this issue open in case it sinks.

Closed because this issue cannot be handled in this project, instead we should have an issue in VSCode.

Closed because Hybrid Mode is mandatory after version 3.0. See #5456.

The Vue version you installed is 3.4. After 3.3, IntrinsicElements was moved to `vue/jsx-runtime`. When your `vueCompilerOptions.target` is specified as 3, you will still try to reference `IntrinsicElements` from `globalThis.JSX.IntrinsicElements`...

I will add workspace diagnostics to report when vueCompilerOptions is inconsistent with the Vue version.

Thanks for the report, but @incutonez/my-package package doesn't seem to exist on npm, could you update the repro case?

Thanks for the PR, but this is an upstream issue: https://github.com/microsoft/TypeScript-TmLanguage/issues/873 We cannot add this patch fix on our side because we cannot maintain of it's complexity. Most importantly, since...