Hey, I was able to find out what was missing and finally got electron-builder to work with my windows icon.ico file, with no jagged results!
The deal was that some add’l config was needed in the builder object of quasar.conf.js. In electron-builder’s documentation, I went to the Windows target page: https://www.electron.build/configuration/win#WindowsConfiguration-target.
From there I found that there is an icon property. Include the ‘win’ object, and include the nested ‘icon’ object with the value being set to the path of your windows ICO file.
icon: ‘src-electron/icons/icon.ico’
My updated quasar.conf.js file (the electron section of it) looks like this now:
electron: {
bundler: 'builder',
extendWebpack (cfg) {
// do something with Electron process Webpack cfg
},
builder: {
// https://www.electron.build/configuration/configuration
appId: 'com.etrac-mss.etrac',
win: {
icon: 'src-electron/icons/icon.ico'
}
}
}
I ran the build, and the installer file looked good. Then I ran the installer and the app icon looks good, too. Phew! Glad to find it’s something simple… (simple after it’s discovered, that is).
I’m wondering if this is something that should get added to Quasar’s documentation for bundling with electron-builder (hmmm, by me?). I guess I would have thought that this would be part of the docs already, or that I’m doing something odd. More likely, it’s an issue of “If you use an external package XYZ, you need to learn about XYZ”.
Here is an image of all my icons (pre and post build/install), and the one icon needed for my Windows distribution need (‘src-electron/icons/icon.ico’).
Big thanks @metalsadman for all your ideas and suggestions - that made a big difference and helped me along!
