Quasar SPA Development

Use this skill with quasar-development for shared application concerns.

Work in SPA mode

1. Inspect quasar.config.*, router history mode, build.publicPath, boot files, and deployment target.
2. Read the current Quasar SPA documentation.
3. Add SPA mode explicitly only when needed: quasar mode add spa.
4. Run locally with quasar dev -m spa; build with quasar build -m spa.

Preserve deployment invariants

• Configure the web server to serve index.html for unknown client-side routes when using history routing.
• Use hash routing when the host cannot provide fallback rewrites and the URL tradeoff is acceptable.
• Align router history, publicPath, asset URLs, and the deployment subdirectory.
• Do not place secrets in client code or build-time client environment variables.
• Lazy-load routes and substantial features; measure bundle output before adding manual chunking.
• Keep offline behavior in PWA mode rather than building an ad hoc service worker into SPA mode.