I have the same problem. Can someone help?

Use for >= 1.0
https://github.com/panstromek/quasar-ide-helper

I have two npm scripts in package.json:
“prepack:win64”: “quasar build -c --mode electron --target win32 --arch x64 --theme mat”
“pack:win64”: "npm run prepack:win64 && electron-builder --win --x64 --project dist/electron-mat/UnPackaged/ --prepackaged …/[app-name]-win32-x64/

You need the “electron-builder” as dev-dependency.

npm run pack:64

@asifm The post is your answer http://forum.quasar-framework.org/post/6229

Ah okay. Thank you!

Have you ever tried “!important” after each css attribute? Same result?

Hello,

I’m currently trying out the next version 0.15 (beta) and wanted to put my current project there. I use in the 0.14 project mixins in the “main.js”. How can I get the smooth into the new structure? Is there a way to include it via the “quasar.conf.js”?

PS: I use the Vue-instance in the mixins.

Hello friends,

I would like to simplify the process of building and deploying my electron app.
With quasar-cli I build the electron app. Now there is a folder with all important files to start the app, e. g. for windows.
I saw at “electron-vue” that they go one step further and create a setup from it. Is there a possibility to store this functionality in the quasar-cli (or in the build-file)?

Furthermore, it would be nice to use quasar-cli to load the builds (setups) onto a server and instruct the client electron app to update itself.
I think “electron-packager” offers such functionality. But not in relation to the Quasar framework.

I would be happy about cool ideas and examples.

@benoitranque Thank you. I was blind.

How can I start with quasar-cli electron or android with 0.15?