Skip to content

Commit ead4aa2

Browse files
committed
update references to volar
1 parent a3eb853 commit ead4aa2

File tree

3 files changed

+8
-4
lines changed

3 files changed

+8
-4
lines changed

src/about/team/members-core.json

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -464,8 +464,12 @@
464464
"title": "Developer",
465465
"projects": [
466466
{
467-
"label": "volar",
468-
"url": "https://github.com/johnsoncodehk/volar"
467+
"label": "@vue/language-tools",
468+
"url": "https://github.com/vuejs/language-tools"
469+
},
470+
{
471+
"label": "Volar.js",
472+
"url": "https://github.com/volarjs"
469473
}
470474
],
471475
"location": "Hong Kong, China",

src/guide/scaling-up/tooling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ If you are looking for a lighter-weight alternative for no-build-step usage, che
5353

5454
## IDE Support {#ide-support}
5555

56-
- The recommended IDE setup is [VSCode](https://code.visualstudio.com/) + the [Volar](https://github.com/johnsoncodehk/volar) extension. Volar provides syntax highlighting, TypeScript support, and intellisense for template expressions and component props.
56+
- The recommended IDE setup is [VSCode](https://code.visualstudio.com/) + the [Vue Language Features (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.volar) extension. The extension provides syntax highlighting, TypeScript support, and intellisense for template expressions and component props.
5757

5858
:::tip
5959
Volar replaces [Vetur](https://marketplace.visualstudio.com/items?itemName=octref.vetur), our previous official VSCode extension for Vue 2. If you have Vetur currently installed, make sure to disable it in Vue 3 projects.

src/guide/typescript/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ With a Vite-based setup, the dev server and the bundler are transpilation-only a
1818

1919
- During development, we recommend relying on a good [IDE setup](#ide-support) for instant feedback on type errors.
2020

21-
- If using SFCs, use the [`vue-tsc`](https://github.com/johnsoncodehk/volar/tree/master/vue-language-tools/vue-tsc) utility for command line type checking and type declaration generation. `vue-tsc` is a wrapper around `tsc`, TypeScript's own command line interface. It works largely the same as `tsc` except that it supports Vue SFCs in addition to TypeScript files. You can run `vue-tsc` in watch mode in parallel to the Vite dev server, or use a Vite plugin like [vite-plugin-checker](https://vite-plugin-checker.netlify.app/) which runs the checks in a separate worker thread.
21+
- If using SFCs, use the [`vue-tsc`](https://github.com/vuejs/language-tools/tree/master/packages/vue-tsc) utility for command line type checking and type declaration generation. `vue-tsc` is a wrapper around `tsc`, TypeScript's own command line interface. It works largely the same as `tsc` except that it supports Vue SFCs in addition to TypeScript files. You can run `vue-tsc` in watch mode in parallel to the Vite dev server, or use a Vite plugin like [vite-plugin-checker](https://vite-plugin-checker.netlify.app/) which runs the checks in a separate worker thread.
2222

2323
- Vue CLI also provides TypeScript support, but is no longer recommended. See [notes below](#note-on-vue-cli-and-ts-loader).
2424

0 commit comments

Comments
 (0)