@electron-forge/cli
module from NPM into your project.electronForge.import
. It will attempt to take an existing Electron app and make it Forge compatible. Normally this just creates a base Electron Forge configuration and adds the required dependencies.There are no flags for the Import command
electronForge.init
, will initialize a new Forge powered application in the given directory (defaults to .
, the current directory).init
command.--template
--copy-ci-files
electronForge.install
, will attempt to install the Electron app that is published at the given GitHub repository. This command is just a helper for installing other applications quickly. For example:electronForge.lint
, will run the lint
command that your package.json
exposes. If the exit code is 0
, no output is shown, otherwise the error output will be displayed.There are no flags for the Lint command
electronForge.make
, will make distributables for your application based on your Forge config and the parameters you pass in.--arch
x64
--platform
mas
--targets
@electron-forge/maker-deb
. By default, the make targets used are the ones available and configured for the given platform.--skip-package
electronForge.package
, will package your application into a platform specific format and put the result in a folder. Please note that this does not make a distributable format. To make proper distributables, please use the make command.--arch
x64
--platform
mas
electronForge.publish
, will attempt to make the forge application and then publish it to the publish targets defined in your forge config.make
artifacts you will have to use the dry-run
options explained below.--target
--dry-run
--from-dry-run
electronForge.start
, will launch the Forge powered application in the given directory (defaults to .
).rs
(and hit enter) in the same terminal where you ran the start command, the running app will be terminated and restarted.--app-path
.
)--enable-logging
--run-as-node
--inspect-electron
--
-- --my-app-argument