0xJacky
5fcad2311b
fix: terminal process not killed #181
|
1 year ago | |
|---|---|---|
| .. | ||
| .vscode | 2 years ago | |
| public | 2 years ago | |
| src | 1 year ago | |
| .env.development | 2 years ago | |
| .env.production | 2 years ago | |
| .gitignore | 1 year ago | |
| .yarnrc.yml | 1 year ago | |
| README.md | 2 years ago | |
| components.d.ts | 1 year ago | |
| frontend.go | 1 year ago | |
| gettext.config.js | 1 year ago | |
| i18n.json | 1 year ago | |
| index.html | 2 years ago | |
| package.json | 1 year ago | |
| tsconfig.json | 2 years ago | |
| tsconfig.node.json | 2 years ago | |
| version.json | 1 year ago | |
| vite.config.ts | 1 year ago | |
| yarn.lock | 1 year ago | |
README.md
Vue 3 + TypeScript + Vite
This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue
3 <script setup> SFCs, check out
the script setup docs to learn more.
Recommended IDE Setup
Type Support For .vue Imports in TS
Since TypeScript cannot handle type information for .vue imports, they are shimmed to be a generic Vue component type
by default. In most cases this is fine if you don't really care about component prop types outside of templates.
However, if you wish to get actual prop types in .vue imports (for example to get props validation when using
manual h(...) calls), you can enable Volar's Take Over mode by following these steps:
- Run
Extensions: Show Built-in Extensionsfrom VS Code's command palette, look forTypeScript and JavaScript Language Features, then right click and selectDisable (Workspace). By default, Take Over mode will enable itself if the default TypeScript extension is disabled. - Reload the VS Code window by running
Developer: Reload Windowfrom the command palette.
You can learn more about Take Over mode here.