See .env.development
for Bazaar mock server configuration variables.
Trying to get the assets generated by the Vite dev server to work offline seems a fools errand. Instead, build for production and serve the dist
files locally. Then, in Chrome dev tools, under Network, set to Offline. It's necessary to build after each change of course.
npx vite build
Using the http-server
NPM package with the following --proxy
option enables history pushstate
for clean URLs in single page applications. Otherwise, all URLs, apart from the home page will 404. In the dist
dir, run:
npx http-server --proxy http://localhost:8080\?
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 Extensions
from VSCode's command palette - Find
TypeScript and JavaScript Language Features
, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Window
from the command palette.
See Vite Configuration Reference.
npm install
npm run dev
npm run build
Run Unit Tests with Vitest
npm run test:unit
Lint with ESLint
npm run lint