Ability to download proper app package based on user's architecture via NSIS

[mastergberry]

As referenced in #1165

If we can change the installer to download the proper app package (32 vs 64 bit) instead of combining both and wasting space then this would be a benefit for people that have large installers.

Objective is to try and save bandwidth for updates/downloads and to make the installation process faster for the user (less download time for people with slow internet).

[mastergberry]

I suppose with this type of feature the updater system will need to have a way to specify whether to download the x32 or x64 bit update as well.

[akashnimare]

+1 for this.

[develar]

Use nsis-web to build web installer. If not nsisWeb.appPackageUrl is not set, web installer is version dependent (because versioned app package is downloaded).

Auto-Update — works as before. Package will be downloaded as part of installing.

[akashnimare]

@develar how do I use it (and autoupdates) if I'm releasing my app on GitHub?

[develar]

In the upcoming version latest.yml will be generated in the nsis-web subdirectory.

[akashnimare]

Let me know when it's released :)

[develar]

@akashnimare Please try 13.6.0

[akashnimare]

@develar How do I suppose to use it? I want to generate both the arch ia32+x64 on windows. Is it correct -

scripts : {
"dist" : "build nsis-web --ia32 --x64"
}

or

scripts : {
"dist" : "build --nsis-web"
}

[develar]

build --win nsis-web --ia32 --x64

[develar]

Or, you can set nsis-web as a default target: set windows.target to ["nsis-web"].

[akashnimare]

Thanks, I'm trying it out 🚀

[akashnimare]

@develar So I have got three files here-

• app Web Setup 0.0.1
• app-0.0.1-ia32.nsis
• app-0.0.1-x64.nsis

and latest.yml in nsis-web directory. I guess I have to upload all these three files + latest.yml in my repo's GitHub release? app Web Setup 0.0.1 is the actual link which I have to give to others to download my app?

[mastergberry]

I'm just curious, is there a way to go from the regular installer to the web installer eventually? Or not possible if you already published the first version of the app?

[develar]

I guess I have to upload all these files + latest.yml in my repo's GitHub release?

Yes. It will be uploaded automatically. https://github.com/electron-userland/electron-builder/wiki/Publishing-Artifacts

app Web Setup 0.0.1 is the actual link which I have to give to others to download my app?

Yes.

is there a way to go from the regular installer to the web installer eventually? Or not possible if you already published the first version of the app?

It is possible without any issues or risks. Because latest.yml contains filename of installer, it will be just downloaded and installed. Auto-updater works with updates as a black box.

Even more — now you can change artifact name, you are not forced to use only web — https://github.com/electron-userland/electron-builder/wiki/Options#NsisWebOptions-artifactName

[akashnimare]

@develar Can I use perMachine and perClick with nsis-web

build : {
    "win": {
      "target": "nsis-web",
      "icon": "build/icon.ico",
      "iconUrl": "https://raw.githubusercontent.com/zulip/zulip-electron/master/build/icon.ico"
    },
    "nsis-web": {
      "perMachine": true,
      "oneClick": false
    }
}

[develar]

You can try and report issue if it doesn't work ;)

[akashnimare]

@develar will update you on this. Btw setting nsis-web in win.target only build for the arch you'are on so I had to use build --win nsis-web --ia32 --x64 to build for both the arch.

[develar]

Btw setting nsis-web in win.target only build for the arch you'are on so I had to use

Yes, it sets only target, not arch. So, build --win --ia32 --x64