Instead of hard-coding it, we could also use the Windows GetCurrentPackageId API. Signing with different certificates will change the ID. The ASCII code after the underscore is a hash of the signing identity and is part of how Windows avoids namespace conflicts. The ID string here can be found by simply creating the package ( conveyor make windows-msix), installing it and then running Get-StartApps from PowerShell. Some can be taken from the package.json files: app We need to specify names, versions and icons. Import package.json files so we can avoid duplicating config. The config file syntax is HOCON, a superset of JSON designed for human convenience. We start by declaring that this is an Electron app and that we’d like to import data from the package.json files in the source tree. We’ll port GitHub Desktop to use Conveyor in these commits: It also requires platform specific code to register URL handlers on Windows.ĭistributing apps with Conveyor is simple, enables cross-building the download/update site for every supported platform from a single machine, and gives us access to some useful features like aggressive updates (checking on each startup). The current packaging solution is based on Electron Packager and requires a fairly large amount of scripting, visible in the build.ts and package.ts files. It also integrates with the Windows notification center. It uses Electron, TypeScript, React, and users can log in using OAuth. GitHub Desktop is a GUI for Git that supports Windows and macOS. The benefits can be seen in the nearly 2,000 lines of code that can be deleted vs the original Squirrel based solution. We’ll also use other GitHub services like Releases, Pages and Actions. Packaging GitHub Desktop lets us see what the configuration looks like for a production-grade app. Distributing Electron apps with Conveyor has a bunch of advantages and doesn’t take long.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |