知学知考阅卷端

Michael Wang 56a6d49f70 检查轨迹分与总分的一致性		4 lat temu
public	da2e3874a5 init project	4 lat temu
src	56a6d49f70 检查轨迹分与总分的一致性	4 lat temu
.gitignore	8783a4c934 add dist.zip to ignore	4 lat temu
README.md	da2e3874a5 init project	4 lat temu
index.html	da2e3874a5 init project	4 lat temu
package.json	314e93c180 update deps	4 lat temu
postcss.config.js	34efdf9593 add tailwindcss	4 lat temu
prettier.config.js	1fc0e2a3f1 prettier	4 lat temu
tailwind.config.js	f5d92baeee tailwind prefix	4 lat temu
tsconfig.json	b448854742 refactor types & resolve alias	4 lat temu
vetur.config.js	fa7315cafe vetur auto import vue components	4 lat temu
vite.config.ts	d9f9e67125 weakedMap 有缓存问题	4 lat temu
yarn.lock	473324f65a update deps	4 lat temu

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