0.1.0-beta.5

@diamonddigitaldev/electron-kit | Beta Preview (v0.1.0-beta.5)

Important

A beta: the API can still change between 0.x versions. It's published under npm's next tag.

Windows shows an app's notifications and groups its windows under its pinned icon, and no ID of the install is left on disk. An app on 0.1.0-beta.4 takes it without a change, but should pass start({ appId }): see below.

npm install @diamonddigitaldev/electron-kit@next

New

• start({ appId }). Windows' app user model ID is now the ID an app passes, which should be its package.json's build.appId. The installer gives the Start menu shortcut that ID, and Windows shows an app's notifications, and groups its windows under its pinned taskbar icon, only when the two match. It's checked as a dotted ID, and set with singleInstance: false too. Pass it: without appId, the ID is the app's name, as before, which matches nothing the installer made.

const kit = require("@diamonddigitaldev/electron-kit/main").start({
    appId: "com.diamonddigitaldev.app", // package.json's build.appId
    // …
});

Privacy

• A .updaterId an earlier version left is deleted. 0.1.0-beta.4 stopped electron-updater making an ID of the install, but left a .updaterId an earlier version had written, unread. Now the updater deletes it as it starts, in a packaged app only, and logs that it did; a failure is one warning. It's still never read or sent.

Docs

• The Main Process: appId, and why it should match build.appId.
• Getting Started: passes one.
• Updates: the ID of the install, and the old file deleted.

The docs are in the repository: start at docs/README.md.

Found something wrong? Open an issue.