shapeshift VS electron-builder

We would be able to leverage our own JVM libraries, namely ShapeShift and a yet-unreleased framework we use for CRUD operations with traditional ORMs and ODMs.

ShapeShift documentation: https://shapeshift.krud.dev/

If you would like to contribute, please feel free to open issues, join as a contributor or star the repository. Thanks in advance!

The good news is we added it to our roadmap (https://github.com/krud-dev/shapeshift/issues/17) and plan to work on it in the near future.

"TL;DR Uni + Freelancer - C# My first paying job, learning to deal with customers Things Un won't teach you: Understand the business 80/20 principle KISS Performance isn't everything Use open source wherever you can Check out my first OpenSource here: https://github.com/krud-dev/shapeshift/"

Please check out my open source library and maybe even star it. I would appreciate it greatly!

In our examples we will use the library ShapeShift. It's a light-weight object mapping library for Kotlin/Java with lots of cool features.

Some time ago our team has released our first open source library to the wild. We finished our first production ready version, posted it on Reddit and waited for the open source community to welcome us with open arms. After all, we are investing our own free time to create a great product to help others, and it's all for FREE.

ShapeShift repository: https://github.com/krud-dev/shapeshift

The last step for each platform's build process is to upload the app to our GitHub releases repository. We automated this step from the beginning, but when we started creating builds for the new M1 chip Macs, we had to add a manual step. This involved merging files needed for the auto-updater to work with the M1 builds.

https://github.com/electron-userland/electron-builder/issues... that issue kinks to the PR that adds the automation.

It's a non-trivial thing to test, since it involves so many secrets and the notarization step can take over an hour, so I don't expect anyone here to actually want to look into it.

My original comment really was just venting my frustration, not a cry for help (but I might be crying soon if I can get to the bottom of this!).

> The ‘autoupdater’ does three things,

>

> - check the app for updates (using Sparkle)

> - report any crashes (using Sentry)

> - start a local HTTP proxy on port 40701 (this can be changed using the configuration json file in the app bundle).

>

> The latter is of course, not to be expected of any app on the machine, especially not one that just claims to be an auto updater.

Well, yes. And no.

For example, electron-builder [^0], a popular framework used for Electron app packaging and auto-updates, uses a local update server on Mac [^1] to add a more sane system backed by a more insane system, Squirrel.

[^0]: https://github.com/electron-userland/electron-builder

[^1]: https://github.com/electron-userland/electron-builder/blob/m...

The Project uses Electorn-Builder to package the app and Electorn-Updater to update.

You can read about this issue here: https://github.com/electron-userland/electron-builder/issues/7114

Ostara is based off of electron-react-boilerplate and uses electron-builder to package the application.

Install electron and electron-builder

I believe Visual Studio Code uses Electron and posts releases on a regular basis. Maybe check their A quick Google search for "electron build github release" turns up "Electron Builder" https://www.electron.build/ I don't really know though; I've never used Electron.

I also would like to have an NSIS installer so if it happens to package the Chromium executable along with my app, how can I accomplish that? I am using electron-builder.

We use electron-builder at work.