> Relying on npm seems a bit awkward.

1. npm solves a few problems here. By publishing to npm, the app is instantly available to be downloaded and installed by users.

2. Auto updating. The launcher will automatically check for updates on launch, and download them if any are found so that users are always working with your latest version.

I may add support for other CDNs - and originally I just had it so you self host. But npm removes a lot fo complexity. It only takes a minute to create an account, and then you can publish.

> I might suggest using native packages, especially on mac; something like a DMG or .package. > Relying on npm seems a bit awkward.

1. npm solves a few problems here. By publishing to npm, the app is instantly available to be downloaded and installed by users.

2. Auto updating. The launcher will automatically check for updates on launch, and download them if any are found so that users are always working with your latest version.

I may add support for other CDNs - and originally I just had it so you self host. But npm removes a lot fo complexity. It only takes a minute to create an account, and then you can publish.

> I might suggest using native packages, especially on mac; something like a DMG or .package

The trouble with DMG and .pkg is that they need to be codesigned and notarized individually - which means you need a Mac and an Apple Developer account. Using jDeploy you don't need a Mac, and you don't need to worry about codesigning. This is because the installer is already signed and notarized. This probably the biggest pain point that I wanted to solve with jDeploy.