Do you have plug-ins installed? They’ll need to be moved to boot files. Otherwise, it’s just moving over your components and router, store, etc. That is all the same.

Scott

Install this package first https://www.npmjs.com/package/npm-run-all

and use following scripts - ‘compress_sw’ is optional

"postbuild": "run-s compress_sw mkdir_wellknown copyfile", "compress_sw": "terser --compress --mangle --output dist/pwa/service-worker.js -- dist/pwa/service-worker.js", "mkdir_wellknown": "mkdir -p /<path to directory>/dist/pwa/.well-known", "copyfile": "cp -r /<path to directory>/src/.well-known/assetlinks.json /<path to directory>/dist/pwa/.well-known/assetlinks.json", ```

You need to register for Discord.

Also, the suggestion/ answer on Discord in the end was to just use Quasar’s CLI to develop the front-end and have the webserver serve the built files. Easy peasy. 🙂

If you are looking to run your own webpack setup, you are missing out on all the work already done within Quasar for you and the big question is then, why are you needing it outside in your own webpack setup? What are you doing, that Quasar can’t?

If you are using Vue separately, then use Quasar as a Vue plugin.

https://quasar.dev/start/vue-cli-plugin

Scott

Hi,
you could try re-install nodeJS (Download the last version - LST) and reinstall quasar

# or $ npm install -g @quasar/cli``` Are you using SO Windows?, maybe is a good idea change npm to Yarn.

Make sure you are in the project folder, when you run the build command.

Scott

Did you tried the icon gini extensin here https://github.com/quasarframework/app-extension-icon-genie/

@tmulle Did you try to use || operator ?

{ build: { distDir: process.env.WEB_BUILD_DIR || 'default/dist/dir', showProgress: process.env.WEB_BUILD_SHOW_PROGRESS || true, scopeHoisting: true, ... // rest of config }, }

@JackyLee nice to know, je vais me coucher moins bête 🙂
1000:1000
UID:GID
1000 usually the first user/group
stackoverflow

quasar build >> /dev/null will turn off all the output

Ok, I looked at https://github.com/pratik227/echarts-quasar and didn’t have to add anything in quasar.conf.js
It just works.

@omgwalt https://we-are.bookmyshow.com/understanding-deep-and-shallow-copy-in-javascript-13438bad941c also to understand more why you need to deep copy/clone https://medium.com/nodesimplified/javascript-pass-by-value-and-pass-by-reference-in-javascript-fcf10305aa9c & https://scotch.io/bar-talk/copying-objects-in-javascript.

I found the solution by placing the js file in statics folder

I finally managed to solve the problem after reading:
“Ensure you have a WKWebView plugin installed: either the official Apache one or Ionic’s. All Ionic starter apps automatically include cordova-plugin-ionic-webview.
Add <preference name=“WKWebViewOnly” value=“true” /> to your config.xml file.
Update each Cordova plugin to the latest version (these can trigger the warning too). Better yet – remove them if they are no longer needed!
Run cordova prepare ios to apply the changes.”

@fringesoft It depends on what you want to do but I think you could take a look at this part of the documentation.

But to answer (partially) your question, I think you can simply run: quasar build --env=dev and then access the result in process.argv to do different things depending on the environment

My thanks to both of you.

Use a boot file. https://quasar.dev/quasar-cli/cli-documentation/boot-files