Questions - electron-builder

[CynthiaBlue]

*** Please read my comment, it is more straightforward than my original question. ***

I'm confused about how to run the build for my project.

The Quasar docs have instructions to use quasar.conf.js configuration. I want to use electron-builder because I want to use the automatic upgrade feater I have read about.

Anyway, building through Quasar I guess I need to use the correct quasar.conf.js code. They have an example for Windows, but not for Mac. I want to build for both on my Mac.
https://quasar.dev/quasar-cli-webpack/developing-electron-apps/build-commands#publishing-electron-builder-only-

   electron: {
      bundler: 'builder', // 'packager' or 'builder'
      packager: {
      },

      builder: {
        appId: 'pawtap',
        "mac": {
          // what goes here?
        },
         "win": {
           target: 'nsis'
         },
      },

      chainWebpackMain (/* chain */) {
      },
      chainWebpackPreload (/* chain */) {
      },
    }

Or... going through electron-builder directly with:
electron-builder --mac
(from this website: https://www.digitalocean.com/community/tutorials/how-to-create-your-first-cross-platform-desktop-application-with-electron-on-macos#step-5-building-your-first-application)

But when I use electron-builder --mac, and try to open the .app I've just created, it gives me an error about my import.

Which is the best way to go, and why?
Thanks!

[CynthiaBlue]

Okay, I've been trying this for hours, and nothing works for windows.

The things I have discovered are:

1 - The command to run the quasar build is: quasar build -m electron -P always

2 - Running the build through quasar you can use either electron-packager or electron-builder. The configurations defined in quasar.conf.js will be used for the builds.

3 - It's also possible to run both packager and builder with their own line commands. I've been trying this, but the windows versions
will not run (I'm running them on my Mac).

4 - Question: is it possible to use the automatic update features of packager & builder if you run the builds through Quasar?

5 - Question: If you run the builds command-line directly using packager & builder, does it know that I am building a Quasar app? When I try it this way, then try to run on Windows (build from Mac) it's telling me the "paw tap.exe" file is missing, so I am wondering if it's really building my application, or is it just building a blank application from the directory I'm in?

6 - Which is the best way to build the application? Though Quasar using packager or builder? Or through the command line for packager or builder? Which do you like best, package or builder?

QUASAR BUILDS:
When running a build through the quasar commands, this is what I have specified in the quasar.conf.js file, below using electron-builder. And this works great running on the Mac, for the Mac. It builds an .app file that runs fine:

electron: {
    bundler: 'builder', // 'packager' or 'builder'
    packager: {
    },
    builder: {
      appId: 'com.electron.pawtap',
      productName: 'Paw Tap',
      mac: {
        target: 'dmg',
      },
    },
    chainWebpackMain (/* chain */) {
    },
    chainWebpackPreload (/* chain */) {
    },
  }

However, when I use the win specifications is not working for me. It doesn't build for Windows:

  win: {
      target: 'nsis',
     },

When I run the above, this is what I see output in my Terminal:

• building        target=macOS zip arch=arm64 file=dist/electron/Packaged/Paw Tap-2.0.1-arm64-mac.zip
• building        target=DMG arch=arm64 file=dist/electron/Packaged/Paw Tap-2.0.1-arm64.dmg
• Detected arm64 process, HFS+ is unavailable. Creating dmg with APFS - supports Mac OSX 10.12+

So I'm assuming that "Detected arm64 process, HFS+ is unavailable" Means that it's reverting to the default and not building windows.

I"m also getting this error:
"Error: Exit code: ENOENT. spawn /usr/bin/python ENOENT UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch()."
But how on earth would I identify which async function doesn't have a catch block? I have a ton of them in my project. And I don't get that error on the Mac build.