Ingen beskrivning

Michael Wang 85ac08a54a fix type warnings		4 år sedan
public	da2e3874a5 init project	4 år sedan
src	85ac08a54a fix type warnings	4 år sedan
.gitignore	4a4a4b1ff5 no more annoying uncommit change	4 år sedan
README.md	da2e3874a5 init project	4 år sedan
index.html	da2e3874a5 init project	4 år sedan
package.json	2f3e600cc0 集成ant-design-vue	4 år sedan
postcss.config.js	34efdf9593 add tailwindcss	4 år sedan
prettier.config.js	1fc0e2a3f1 prettier	4 år sedan
tailwind.config.js	f5d92baeee tailwind prefix	4 år sedan
tsconfig.json	b448854742 refactor types & resolve alias	4 år sedan
vetur.config.js	1fc0e2a3f1 prettier	4 år sedan
vite.config.ts	eb032a1985 conf for admin pages	4 år sedan
yarn.lock	2f3e600cc0 集成ant-design-vue	4 år sedan

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-vue to the plugins section in tsconfig.json
Delete src/shims-vue.d.ts as it is no longer needed to provide module info to Typescript
Open src/main.ts in VSCode
Open the VSCode command palette
Search and run "Select TypeScript version" -> "Use workspace version"

README.md