flatpak key contains a set of options instructing electron-builder on how it should build a Flatpak bundle.
Build dependenciesThe
flatpak and flatpak-builder packages need to be installed in order to build Flatpak bundles.Troubleshooting
If the Flatpak build process fails with an error message like “flatpak failed with status code X”, setting theDEBUG="@malept/flatpak-bundler" environment variable should provide more context about the error.
Configuration
The path to EULA license file. Defaults to
license.txt or eula.txt (or uppercase variants). Only plain text is supported.The name of the runtime that the application uses.See flatpak manifest documentation.
The version of the runtime that the application uses.See flatpak manifest documentation.
The name of the development runtime that the application builds with.See flatpak manifest documentation.
Start with the files from the specified application. This can be used to create applications that extend another application.See flatpak manifest documentation.
Use this specific version of the application specified in base.See flatpak manifest documentation.
The branch to use when exporting the application.See flatpak manifest documentation.
An array of arguments passed to the flatpak build-finish command.See flatpak manifest documentation.
An array of objects specifying the modules to be built in order.See flatpak manifest documentation.
Files to copy directly into the app. Should be a list of [source, dest] tuples. Source should be a relative/absolute path to a file/directory to copy into the flatpak, and dest should be the path inside the app install prefix (e.g. /share/applications/).See @malept/flatpak-bundler documentation.
Symlinks to create in the app files. Should be a list of [target, location] symlink tuples. Target can be either a relative or absolute path inside the app install prefix, and location should be a absolute path inside the prefix to create the symlink at.See @malept/flatpak-bundler documentation.
Whether to enable the Wayland specific flags (
--enable-features=UseOzonePlatform --ozone-platform=wayland) in the wrapper script. These flags are only available starting with Electron version 12.The short description.
As description from application package.json, but allows you to specify different for Linux.
The application category.
The mime types in addition to specified in the file associations. Use it if you don’t want to register a new mime type, but reuse existing.
The Desktop file
The executable parameters. Pass to executableName