Vue 3 + Quasar v2 SPA used as an investor-facing microsite (project, invest, roadmap pages).
Versions are enforced in package.json under engines. Use a matching Node runtime before installing dependencies.
| Tool | Supported versions |
|---|---|
| Node.js | 22.12+ (22.x), or 24.x, 26.x, 28.x |
| npm | ≥ 6.13.4 (ships with Node; use current LTS npm when possible) |
| pnpm | ≥ 10.0.0 (optional) |
| Yarn | ≥ 1.21.1 (optional) |
Examples that satisfy the engine range: 22.20, 24.x, 26.x, 28.x.
Node 22.0–22.11 is not listed in engines and may fail npm install if strict engine checks are enabled.
Check your versions:
node -v # e.g. v22.20.0 or v24.x.x
npm -vNo global install is required for normal work on this repo.
After dependencies are installed, the Quasar CLI from @quasar/app-vite (devDependency) is available as:
npm run dev— development servernpm run build— production build
Those scripts run the local quasar binary from node_modules/.bin.
Optional: install the global CLI if you want the quasar command everywhere in your shell:
npm install -g @quasar/cliThen you can run quasar dev / quasar build from the project root instead of npm run …. Functionally it is the same as using the npm scripts after npm install.
npm installOr, if you use pnpm / Yarn and meet the engines versions:
pnpm install
# or
yarnpostinstall runs quasar prepare (Quasar project setup).
npm run devOpens the Quasar dev server (see quasar.config.js → devServer).
npm run buildOutput is written under dist/spa/ by default.
- Quasar / Vite: quasar.config.js in the project root
- Site copy / contact:
src/constants/site.js - Routes:
src/router/routes.js
All hero and contact forms persist to project xlgiwuqgjcefpamjulsp.
cp .env.example .env.local
# Set VITE_SUPABASE_ANON_KEY from Dashboard → Settings → API (anon public)
npm run devFull setup, table map, CI secrets, and troubleshooting: supabase/README.md.
Sitemap, robots, meta tags, and Search Console steps: SEARCH_ENGINE_SETUP.md.