This template should help get you started developing with Vue 3 in Vite.
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
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:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
See Vite Configuration Reference.
npm installnpm run devnpm run buildRun Unit Tests with Vitest
npm run test:unitRun End-to-End Tests with Cypress
npm run test:e2e:devThis 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:e2eLint with ESLint
npm run lintsteps:
yarn init Vue@latestyarn init v1.22.19
question name (bs5vue): vuefun
√ Add an End-to-End Testing Solution? » Cypress
√ Add ESLint for code quality? ... No / Yes
√ Add Prettier for code formatting? ... No / Yes
Scaffolding project in C:\dev2\learn\bs5vue\vue-fundamentals...
Done. Now run:
cd vue-fundamentals
npm install
npm run lint
npm run dev yarngh repo create BOT-TC/vue-fundamenals --public
gh repo list BOT-TC
git remote add origin https://github.com/BOT-TC/vue-fundamenals.git
git branch -M main
git push -u origin main- Setup Supabase Cloud Project
- Setup Local Project
supabase login
(you will need your account access token you generated)
supabase link --project-ref [Reference ID] -p [DB_PASSWORD]
supabase db remote commit
?? one or both of the following
supabase db push
supabase db resetNOTE: You can change configuration using the /supabase/config.toml file. NOTE: You can access the email via the port in the conf. since it does actuall get sent.