Quasar Framework and Web Server: SPA Asset Resolution in Non-Root Subdirectories

Production Deployment Path Configuration

A Quasar Framework application typically functions correctly during local development using the dev server. However, when deploying a production SPA build to a web server where the application is hosted in a non-root subdirectory (e.g., /app-name/), asset resolution often fails.

The challenge involves ensuring that the bundled JavaScript and CSS files are referenced using paths that remain valid regardless of the server's directory structure, while maintaining compatibility with the Vue Router's base path configuration.

Given the build process in quasar.config.js, what is the precise configuration required to synchronize the public path of static assets with the router's base URL for a subdirectory deployment? How does this affect the resolution of absolute paths versus relative paths in the final production bundle?