You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
mhsnet b5ebf45d9d
3d项目上传
1 year ago
..
.vscode 3d项目上传 1 year ago
cypress 3d项目上传 1 year ago
public 3d项目上传 1 year ago
src 3d项目上传 1 year ago
.eslintrc.cjs 3d项目上传 1 year ago
.gitignore 3d项目上传 1 year ago
.prettierrc.json 3d项目上传 1 year ago
README.md 3d项目上传 1 year ago
cypress.config.ts 3d项目上传 1 year ago
env.d.ts 3d项目上传 1 year ago
index.html 3d项目上传 1 year ago
package.json 3d项目上传 1 year ago
tsconfig.app.json 3d项目上传 1 year ago
tsconfig.json 3d项目上传 1 year ago
tsconfig.node.json 3d项目上传 1 year ago
tsconfig.vitest.json 3d项目上传 1 year ago
vite.config.ts 3d项目上传 1 year ago
vitest.config.ts 3d项目上传 1 year ago
yarn.lock 3d项目上传 1 year ago

README.md

vue3-pro

This template should help get you started developing with Vue 3 in Vite.

VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).

Type Support for .vue Imports in TS

TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:

  1. Disable the built-in TypeScript Extension
    1. Run Extensions: Show Built-in Extensions from VSCode's command palette
    2. Find TypeScript and JavaScript Language Features, right click and select Disable (Workspace)
  2. Reload the VSCode window by running Developer: Reload Window from the command palette.

Customize configuration

See Vite Configuration Reference.

Project Setup

npm install

Compile and Hot-Reload for Development

npm run dev

Type-Check, Compile and Minify for Production

npm run build

Run Unit Tests with Vitest

npm run test:unit

Run End-to-End Tests with Cypress

npm run test:e2e:dev

This runs the end-to-end tests against the Vite development server. It is much faster than the production build.

But it's still recommended to test the production build with test:e2e before deploying (e.g. in CI environments):

npm run build
npm run test:e2e

Lint with ESLint

npm run lint