Maybe try resolve or path.resolve? extendWebpack (cfg) { cfg.resolve.alias = { ...cfg.resolve.alias, // Add your own alias like this 'vue$': 'vue/dist/vue.esm.js', '@': resolve('src') } or… extendWebpack (cfg) { cfg.resolve.alias = { ...cfg.resolve.alias, // Add your own alias like this 'vue$': 'vue/dist/vue.esm.js', '@': path.resolve('src') }

Updating Quasar to 0.17.6 solved the issue.

Use a .env file for local development/docker-compose etc .env export APP_API_HOST=http://localhost export APP_API_PORT=8080 Change the above values during deployment depending on your environment. $ source .env quasar.conf.js build: { env: { APP_API_HOST: JSON.stringify(process.env.APP_API_HOST), APP_API_PORT: JSON.stringify(process.env.APP_API_PORT) }, If you are deploying using GitlabCI/Docker/K8s or whatever environment injection is probably what you are after anyway.

@mzamateo said in Deploy and upgrade quasar app: you can ask kindly to finish current work and then reload, with a popup or so… Exactly ! On my side, I put app version in localstorage (or cookie) and I check if the current version is different (ex: 9.0.10 -> 9.0.11) then I open dialog to inform the user that a new version is available since his last visit and if he want to see the changelog or not.

I’m glad you figured things out. Was about to contact you so I can take a look now, but you were faster