w, -which-module A specific module to build, or comma separated m, -module-dir The path to the app directory to rebuild a, -arch Override the target architecture to something f, -force Force rebuilding modules, even if we would skip v, -version The version of Electron to build against e debugĮ debug runs your local Electron build inside of lldb or gdb.Usage: electron-rebuild -version -module-dir For example,Į node -version will print out Electron's node version. Any extraĪrgs are passed along to ninja, so for example e build -vĪfter you've built Electron, it's time to use it! CommandĪs usual, any extra args are passed along to the executable. These build targets are supported: Targetīuilds the Electron binary and generates a dist zip fileĪs with syncing, e build is usually all you need. Once you have the source, the next step is to build it with e build. To see all potential options for this command, run: Get / update / synchronize source code branchesĮ init initializes a new local development environment for Electron. e wraps these tools: CommandĬreate a new build config and initialize a GN directory Uses Chromium's Depot Tools and GN for wranglingĪnd building the code. A source tree needs to have all of theĪbove and for their versions to be in sync with each other. Getting the source code is a lot more than cloning electron/electron.Įlectron is built on top of Chromium (with Electron patches) and Node Show which configuration is currently in useĬhange which configuration is currently in use Have multiple build configurations and manage them in a way similar to nvm: nvm

Clang's asan or tsan)Į holds all these variables together in a build configuration. That you can switch between so that one is the current, active configuration. See e -help or e help Į also borrows another inspiration from nvm: having multiple configurations You'll invoke e with commands and subcommands. While you're waiting, grab aĬup of hot caffeine and read about what your computer is doing: ConceptsĮlectron's build-tools command is named e.

`~/electron-gn/main`)Į init -root= ~/electron -bootstrap testing # If you're going to use multiple branches, you may want something like: # `-root=~/electron/branch` (e.g. # You can specify any path you like this command defaults to `$PWD/electron`. # The 'Hello, World!' of build-tools: get and build `main` # Choose the directory where Electron's source and build files will reside.

Npm i electron