History

Jef Roosens fd6b3ed134 continuous-integration/drone the build was successful Details Added yarn.lock file		2021-05-01 21:34:41 +02:00
..
public	…
src	Fixed eslint errors	2021-05-01 21:22:12 +02:00
.env	[#44 ] Fixed development .env file	2021-04-29 11:37:35 +02:00
.env.production	…
.eslintrc.yml	[#58 ] Added ESLint & ran formatter	2021-05-01 19:09:58 +02:00
.gitignore	…
README.md	…
index.html	Simplified Ivago API wrapper in frontend	2021-04-30 00:24:19 +02:00
package.json	Fixed frontend linter	2021-05-01 21:11:13 +02:00
tsconfig.json	…
vite.config.ts	…
yarn.lock	Added yarn.lock file	2021-05-01 21:34:41 +02:00

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

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"