goploy/web
2022-04-21 10:37:37 +08:00
..
public A web 2021-05-27 17:05:57 +08:00
src U ssh support password 2022-04-21 10:37:37 +08:00
.env.development A web 2021-05-27 17:05:57 +08:00
.env.production A web 2021-05-27 17:05:57 +08:00
.eslintrc.json U type define 2022-04-01 10:12:44 +08:00
.gitignore A web 2021-05-27 17:05:57 +08:00
.prettierrc.json A web 2021-05-27 17:05:57 +08:00
babel.config.js A web 2021-05-27 17:05:57 +08:00
index.html A server configuration 2021-09-18 16:35:50 +08:00
package-lock.json U package 2022-03-31 18:59:23 +08:00
package.json U package 2022-03-31 18:59:23 +08:00
README.md A web 2021-05-27 17:05:57 +08:00
tsconfig.json U import server 2022-03-17 21:09:12 +08:00
vite.config.ts F local storage 2021-07-04 10:25:30 +08:00
Web.go A web 2021-05-27 17:05:57 +08:00

Vue 3 + Typescript + Vite

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

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"