Electron packaging (start creating desktop app releases)

[1j01]

I want to start producing builds early. I can copy a lot of boilerplate/configuration from jspaint.

Electron and Electron Forge both pretend to be way simpler than they are in practice, but what are you gonna do?

[1j01]

• [x] Fix the build https://github.com/1j01/tracky-mouse/issues/53
• [x] Fix icons in packaged app. I tried a symlink, but Electron Forge broke. I could make the images folder into an internal "resources" npm package, or I could just copy the needed icons into the app. I don't expect to change them frequently, and it would be nice to have a clean separation of what is required by the app, in order to limit the size of the app.
• [x] Handle Squirrel events properly. Don't require serenade-driver or anything until after exit for installer, since if it errors, it's pretty ugly, and may even leave the installer process running. Exit properly. app.quit() doesn't exit immediately!
• [x] Prevent click at startup — especially since the non-traditional Windows installer installs and runs the app in one click! —through some combination of:
  • [ ] #41
  • [x] https://github.com/1j01/tracky-mouse/issues/10
  • [ ] or a welcome screen
  • [ ] or SOMETHING
• [x] Establish some sort of release process
• [x] I should make sure the npm package has a README. I've moved it into a folder, so the README is no longer next to the package.json file. Maybe the API.md can become the readme of the library?

[1j01]

Released the first prebuilt version of the desktop app, in v1.1.0