Nincs leírás

Michael Wang b7c46b7050 fix: z-index层级遮盖 4 éve
public da2e3874a5 init project 4 éve
src b7c46b7050 fix: z-index层级遮盖 4 éve
.gitignore 8783a4c934 add dist.zip to ignore 4 éve
README.md da2e3874a5 init project 4 éve
index.html cb209dbfc1 单任务复核 4 éve
package.json a9021a6211 update deps 4 éve
postcss.config.js 34efdf9593 add tailwindcss 4 éve
prettier.config.js 1fc0e2a3f1 prettier 4 éve
tailwind.config.js f5d92baeee tailwind prefix 4 éve
tsconfig.json b448854742 refactor types & resolve alias 4 éve
vetur.config.js fa7315cafe vetur auto import vue components 4 éve
vite.config.ts 1431d77055 update vite 2.3.0 to avoid security holes 4 éve
yarn.lock a9021a6211 update deps 4 éve

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

  1. Install and add @vuedx/typescript-plugin-vue to the plugins section in tsconfig.json
  2. Delete src/shims-vue.d.ts as it is no longer needed to provide module info to Typescript
  3. Open src/main.ts in VSCode
  4. Open the VSCode command palette
  5. Search and run "Select TypeScript version" -> "Use workspace version"