Quick Start

    By the end of this tutorial, your app will open a browser window that displays a web page with information about which Chromium, Node.js, and Electron versions are running.

    To use Electron, you need to install Node.js. We recommend that you use the latest LTS version available.

    To check that Node.js was installed correctly, type the following commands in your terminal client:

    The commands should print the versions of Node.js and npm accordingly.

    Note: Since Electron embeds Node.js into its binary, the version of Node.js running your code is unrelated to the version running on your system.

    Create your application

    Electron apps follow the same general structure as other Node.js projects. Start by creating a folder and initializing an npm package.

    ```sh npm2yarn mkdir my-electron-app && cd my-electron-app npm init

    2. The interactive `init` command will prompt you to set some fields in your config.
    3. There are a few rules to follow for the purposes of this tutorial:
    5. * `entry point` should be `main.js`.
    6. * `author` and `description` can be any value, but are necessary for
    7. [app packaging](#package-and-distribute-your-application).
    9. Your `package.json` file should look something like this:
    11. ```json
    12. {
    13.   "name": "my-electron-app",
    14.   "version": "1.0.0",
    15.   "description": "Hello World!",
    16.   "main": "main.js",
    17.   "author": "Jane Doe",
    18.   "license": "MIT"
    19. }

    Then, install the electron package into your app’s devDependencies.

    ```sh npm2yarn $ npm install —save-dev electron

    2. > Note: If you're encountering any issues with installing Electron, please
    3. > refer to the [Advanced Installation][advanced-installation] guide.
    5. Finally, you want to be able to execute Electron. In the [`scripts`][package-scripts]
    6. field of your `package.json` config, add a `start` command like so:
    8. ```json
    9. {
    10.   "scripts": {
    11.     "start": "electron ."
    12.   }
    13. }

    This start command will let you open your app in development mode.

    ```sh npm2yarn npm start

    2. > Note: This script tells Electron to run on your project's root folder. At this stage,
    3. > your app will immediately throw an error telling you that it cannot find an app to run.
    5. [advanced-installation]: ./installation.md
    6. [package-scripts]: https://docs.npmjs.com/cli/v7/using-npm/scripts
    8. ### Run the main process
    10. The entry point of any Electron application is its `main` script. This script controls the
    11. **main process**, which runs in a full Node.js environment and is responsible for
    12. controlling your app's lifecycle, displaying native interfaces, performing privileged
    13. operations, and managing renderer processes (more on that later).
    15. During execution, Electron will look for this script in the [`main`][package-json-main]
    16. field of the app's `package.json` config, which you should have configured during the
    17. [app scaffolding](#scaffold-the-project) step.
    19. To initialize the `main` script, create an empty file named `main.js` in the root folder
    20. of your project.
    22. > Note: If you run the `start` script again at this point, your app will no longer throw
    23. > any errors! However, it won't do anything yet because we haven't added any code into
    24. > `main.js`.
    26. [package-json-main]: https://docs.npmjs.com/cli/v7/configuring-npm/package-json#main
    28. ### Create a web page
    29. Before we can create a window for our application, we need to create the content that
    30. will be loaded into it. In Electron, each window displays web contents that can be loaded
    31. from either a local HTML file or a remote URL.
    33. For this tutorial, you will be doing the former. Create an `index.html` file in the root
    34. folder of your project:
    36. ```html
    37. <!DOCTYPE html>
    38. <html>
    39.   <head>
    40.     <meta charset="UTF-8">
    41.     <!-- https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP -->
    42.     <meta http-equiv="Content-Security-Policy" content="default-src 'self'; script-src 'self'">
    43.     <meta http-equiv="X-Content-Security-Policy" content="default-src 'self'; script-src 'self'">
    45.   </head>
    46.   <body>
    47.     <h1>Hello World!</h1>
    48.     We are using Node.js <span id="node-version"></span>,
    49.     Chromium <span id="chrome-version"></span>,
    50.     and Electron <span id="electron-version"></span>.
    51.   </body>
    52. </html>

    Note: Looking at this HTML document, you can observe that the version numbers are missing from the body text. We’ll manually insert them later using JavaScript.

    Opening your web page in a browser window

    Now that you have a web page, load it into an application window. To do so, you’ll need two Electron modules:

    • The module, which controls your application’s event lifecycle.
    • The BrowserWindow module, which creates and manages application windows.

    Because the main process runs Node.js, you can import these as modules at the top of your file:

    1. const { app, BrowserWindow } = require('electron')

    Next, call this createWindow() function to open your window.

    In Electron, browser windows can only be created after the app module’s ready event is fired. You can wait for this event by using the API. Call createWindow() after whenReady() resolves its Promise.

    1. app.whenReady().then(() => {
    2.   createWindow()
    3. })

    Although you can now open a browser window, you’ll need some additional boilerplate code to make it feel more native to each platform. Application windows behave differently on each OS, and Electron puts the responsibility on developers to implement these conventions in their app.

    In general, you can use the process global’s platform attribute to run code specifically for certain operating systems.

    Quit the app when all windows are closed (Windows & Linux)

    On Windows and Linux, exiting all windows generally quits an application entirely.

    To implement this, listen for the app module’s 'window-all-closed' event, and call if the user is not on macOS (darwin).

    1. app.on('window-all-closed', () => {
    2.   if (process.platform !== 'darwin') app.quit()
    3. })

    Open a window if none are open (macOS)

    Whereas Linux and Windows apps quit when they have no windows open, macOS apps generally continue running even without any windows open, and activating the app when no windows are available should open a new one.

    To implement this feature, listen for the app module’s event, and call your existing createWindow() method if no browser windows are open.

    Because windows cannot be created before the ready event, you should only listen for activate events after your app is initialized. Do this by attaching your event listener from within your existing whenReady() callback.

    1. app.whenReady().then(() => {
    2.   createWindow()
    4.   app.on('activate', () => {
    5.     if (BrowserWindow.getAllWindows().length === 0) createWindow()
    6.   })
    7. })

    Note: At this point, your window controls should be fully functional!

    Access Node.js from the renderer with a preload script

    Now, the last thing to do is print out the version numbers for Electron and its dependencies onto your web page.

    Accessing this information is trivial to do in the main process through Node’s global process object. However, you can’t just edit the DOM from the main process because it has no access to the renderer’s document context. They’re in entirely different processes!

    This is where attaching a preload script to your renderer comes in handy. A preload script runs before the renderer process is loaded, and has access to both renderer globals (e.g. window and document) and a Node.js environment.

    1. window.addEventListener('DOMContentLoaded', () => {
    2.   const replaceText = (selector, text) => {
    3.     const element = document.getElementById(selector)
    4.     if (element) element.innerText = text
    5.   }
    7.   for (const dependency of ['chrome', 'node', 'electron']) {
    8.     replaceText(`${dependency}-version`, process.versions[dependency])
    9.   }
    10. })

    The above code accesses the Node.js process.versions object and runs a basic replaceText helper function to insert the version numbers into the HTML document.

    To attach this script to your renderer process, pass in the path to your preload script to the webPreferences.preload option in your existing BrowserWindow constructor.

    There are two Node.js concepts that are used here:

    • The string points to the path of the currently executing script (in this case, your project’s root folder).
    • The path.join API joins multiple path segments together, creating a combined path string that works across all platforms.

    We use a path relative to the currently executing JavaScript file so that your relative path will work in both development and packaged mode.

    At this point, you might be wondering how to add more functionality to your application.

    For any interactions with your web contents, you want to add scripts to your renderer process. Because the renderer runs in a normal web environment, you can add a <script> tag right before your index.html file’s closing </body> tag to include any arbitrary scripts you want:

    1. <script src="./renderer.js"></script>

    The code contained in renderer.js can then use the same JavaScript APIs and tooling you use for typical front-end development, such as using to bundle and minify your code or React to manage your user interfaces.

    Recap

    After following the above steps, you should have a fully functional Electron application that looks like this:

    The full code is available below:

    1. // main.js
    3. // Modules to control application life and create native browser window
    4. const { app, BrowserWindow } = require('electron')
    5. const path = require('path')
    7. const createWindow = () => {
    8.   // Create the browser window.
    10.     width: 800,
    11.     height: 600,
    12.     webPreferences: {
    13.       preload: path.join(__dirname, 'preload.js')
    14.     }
    15.   })
    17.   // and load the index.html of the app.
    19.   // Open the DevTools.
    20.   // mainWindow.webContents.openDevTools()
    21. }
    23. // This method will be called when Electron has finished
    24. // initialization and is ready to create browser windows.
    25. // Some APIs can only be used after this event occurs.
    26. app.whenReady().then(() => {
    27.   createWindow()
    29.   app.on('activate', () => {
    30.     // On macOS it's common to re-create a window in the app when the
    31.     // dock icon is clicked and there are no other windows open.
    32.     if (BrowserWindow.getAllWindows().length === 0) createWindow()
    33.   })
    34. })
    36. // Quit when all windows are closed, except on macOS. There, it's common
    37. // for applications and their menu bar to stay active until the user quits
    38. // explicitly with Cmd + Q.
    39. app.on('window-all-closed', () => {
    40.   if (process.platform !== 'darwin') app.quit()
    41. })
    43. // In this file you can include the rest of your app's specific main process
    44. // code. You can also put them in separate files and require them here.
    1. // preload.js
    3. // All of the Node.js APIs are available in the preload process.
    4. // It has the same sandbox as a Chrome extension.
    5. window.addEventListener('DOMContentLoaded', () => {
    6.   const replaceText = (selector, text) => {
    7.     const element = document.getElementById(selector)
    8.     if (element) element.innerText = text
    9.   }
    11.   for (const dependency of ['chrome', 'node', 'electron']) {
    12.     replaceText(`${dependency}-version`, process.versions[dependency])
    13.   }
    14. })
    1. <!--index.html-->
    3. <!DOCTYPE html>
    4. <html>
    5.   <head>
    6.     <meta charset="UTF-8">
    7.     <!-- https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP -->
    8.     <meta http-equiv="Content-Security-Policy" content="default-src 'self'; script-src 'self'">
    9.     <meta http-equiv="X-Content-Security-Policy" content="default-src 'self'; script-src 'self'">
    10.     <title>Hello World!</title>
    11.   </head>
    12.   <body>
    13.     <h1>Hello World!</h1>
    14.     We are using Node.js <span id="node-version"></span>,
    15.     Chromium <span id="chrome-version"></span>,
    16.     and Electron <span id="electron-version"></span>.
    18.     <!-- You can also require other files to run in this process -->
    19.     <script src="./renderer.js"></script>
    20.   </body>
    21. </html>

    ```fiddle docs/fiddles/quick-start

    1. Create a distributable using Forge’s make command:

      ```sh npm2yarn npm run make

      my-electron-app@1.0.0 make /my-electron-app electron-forge make

      ✔ Checking your system ✔ Resolving Forge Config We need to package your application before we can make it ✔ Preparing to Package Application for arch: x64 ✔ Preparing native dependencies ✔ Packaging Application Making for the following targets: zip ✔ Making for target: zip - On platform: darwin - For arch: x64

      2. Electron Forge creates the `out` folder where your package will be located:
      4. ```plain
      5. // Example for macOS
      6. out/
      7. ├── out/make/zip/darwin/x64/my-electron-app-darwin-x64-1.0.0.zip