diff --git a/src/guide/typescript/overview.md b/src/guide/typescript/overview.md index 22a7f9c9a7..89835788c6 100644 --- a/src/guide/typescript/overview.md +++ b/src/guide/typescript/overview.md @@ -57,7 +57,7 @@ See also: > This section only applies for VSCode + Volar. -To get Vue SFCs and TypeScript working together, Volar creates a separate TS language service instance patched with Vue-specific support, and uses it in Vue SFCs. At the same time, plain TS files are still handled by VSCode's built-in TS language service, which is why we need [TypeScript Vue Plugin](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin) to support Vue SFC imports in TS files. This default setup works, but for each project we are running two TS language service instances: one from Volar, one from VSCode's built-in service. This is a bit inefficient and can lead to performance issues in large projects. +To get Vue SFCs and TypeScript working together, Volar creates a separate TS language service instance patched with Vue-specific support, and uses it in Vue SFCs. At the same time, plain TS files are still handled by VSCode's built-in TS language service, which is why we need [Vue Language Features (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.volar) to support Vue SFC imports in TS files. This default setup works, but for each project we are running two TS language service instances: one from Volar, one from VSCode's built-in service. This is a bit inefficient and can lead to performance issues in large projects. Volar provides a feature called "Takeover Mode" to improve performance. In takeover mode, Volar provides support for both Vue and TS files using a single TS language service instance. @@ -71,6 +71,8 @@ To enable Takeover Mode, you need to disable VSCode's built-in TS language servi +Note: Once takeover mode is activated, you no longer need Typescript Vue Plugin (Volar) + ### Note on Vue CLI and `ts-loader` In webpack-based setups such as Vue CLI, it is common to perform type checking as part of the module transform pipeline, for example with `ts-loader`. This, however, isn't a clean solution because the type system needs knowledge of the entire module graph to perform type checks. Individual module's transform step simply is not the right place for the task. It leads to the following problems: