Michael Wang
b7e96286a6
style refactor to class
|
il y a 4 ans | |
|---|---|---|
| public | il y a 4 ans | |
| src | il y a 4 ans | |
| .gitignore | il y a 4 ans | |
| README.md | il y a 4 ans | |
| index.html | il y a 4 ans | |
| package.json | il y a 4 ans | |
| postcss.config.js | il y a 4 ans | |
| prettier.config.js | il y a 4 ans | |
| tailwind.config.js | il y a 4 ans | |
| tsconfig.json | il y a 4 ans | |
| vetur.config.js | il y a 4 ans | |
| vite.config.ts | il y a 4 ans | |
| yarn.lock | il y a 4 ans |
README.md
Vue 3 + Typescript + Vite
This template should help get you started developing with Vue 3 and Typescript in Vite.
Recommended IDE Setup
VSCode + Vetur. Make sure to enable vetur.experimental.templateInterpolationService in settings!
If Using <script setup>
<script setup> is a feature that is currently in RFC stage. To get proper IDE support for the syntax, use Volar instead of Vetur (and disable Vetur).
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 use the following:
If Using Volar
Run Volar: Switch TS Plugin on/off from VSCode command palette.
If Using Vetur
- Install and add
@vuedx/typescript-plugin-vueto the plugins section intsconfig.json - Delete
src/shims-vue.d.tsas it is no longer needed to provide module info to Typescript - Open
src/main.tsin VSCode - Open the VSCode command palette
- Search and run "Select TypeScript version" -> "Use workspace version"