License: MIT

Language: JavaScript

A boilerplate for Scalable Cross-Platform Desktop Apps based on Electron, React, Redux, React Router, Webpack and React Transform HMR for rapid application development.

Build Status Appveyor Build Status Dependency Status Github Tag Join the chat at OpenCollective OpenCollective

Electron Boilerplate Demo


  • If you have installation or compilation issues with this project, please see our debugging guide

First, clone the repo via git:

git clone --depth=1 your-project-name

And then install dependencies with yarn.

$ cd your-project-name
$ yarn


Start the app in the dev environment. This starts the renderer process in hot-module-replacement mode and starts a webpack dev server that sends hot updates to the renderer process:

$ yarn dev

Alternatively, you can run the renderer and main processes separately. This way, you can restart one process without waiting for the other. Run these two commands simultaneously in different console tabs:

$ yarn start-renderer-dev
$ yarn start-main-dev

If you don't need autofocus when your files was changed, then run dev with env START_MINIMIZED=true:

$ START_MINIMIZED=true yarn dev


To package apps for the local platform:

$ yarn package

To package apps for all platforms:

First, refer to Multi Platform Build for dependencies.


$ yarn package-all

To package apps with options:

$ yarn package -- --[option]

To run End-to-End Test

$ yarn build
$ yarn test-e2e

# Running e2e tests in a minimized window
$ START_MINIMIZED=true yarn build
$ yarn test-e2e

💡 You can debug your production build with devtools by simply setting the DEBUG_PROD env variable:

DEBUG_PROD=true yarn package

How to add modules to the project

You will need to add other modules to this boilerplate, depending on the requirements of your project. For example, you may want to add node-postgres to communicate with PostgreSQL database, or material-ui to reuse react UI components.

⚠️ Please read the following section before installing any dependencies ⚠️

Module Structure

This boilerplate uses a two package.json structure. This means, you will have two package.json files.

  1. ./package.json in the root of your project
  2. ./app/package.json inside app folder

Which package.json file to use

Rule of thumb is: all modules go into ./package.json except native modules, or modules with native dependencies or peer dependencies. Native modules, or packages with native dependencies should go into ./app/package.json.

  1. If the module is native to a platform (like node-postgres), it should be listed under dependencies in ./app/package.json
  2. If a module is imported by another module, include it in dependencies in ./package.json. See this ESLint rule. Examples of such modules are material-ui, redux-form, and moment.
  3. Otherwise, modules used for building, testing and debugging should be included in devDependencies in ./package.json.

Further Readings

See the wiki page, Module Structure — Two package.json Structure to understand what is native module, the rationale behind two package.json structure and more.

For an example app that uses this boilerplate and packages native dependencies, see erb-sqlite-example.

CSS Modules

This boilerplate is configured to use css-modules out of the box.

All .css file extensions will use css-modules unless it has .global.css.

If you need global styles, stylesheets with .global.css will not go through the css-modules loader. e.g.

If you want to import global css libraries (like bootstrap), you can just write the following code in .global.css:

@import '~bootstrap/dist/css/bootstrap.css';

Sass support

If you want to use Sass in your app, you only need to import .sass files instead of .css once:

import './';

Static Type Checking

This project comes with Flow support out of the box! You can annotate your code with types, get Flow errors as ESLint errors, and get type errors during runtime during development. Types are completely optional.

Dispatching redux actions from main process

See #118 and #108

How to keep your project updated with the boilerplate

If your application is a fork from this repo, you can add this repo to another git remote:

git remote add upstream

Then, use git to merge some latest commits:

git pull upstream master



Support us with a monthly donation and help us continue our activities. [Become a backer]


Become a sponsor and get your logo on our README on Github with a link to your site. [Become a sponsor]


MIT © C. T. Lin

Project Statistics

Sourcerank 2
Repository Size 5.51 MB
Stars 0
Forks 0
Watchers 1
Open issues 0
Dependencies 1,863
Contributors 84
Tags 0
Last updated
Last pushed

Top Contributors See all

C. T. Lin Amila Welihinda Jhen-Jie Hong Greenkeeper zeevl MeMark2 Dustin Townsend Dominik Schmidt xwartz kubijo Andrew Kovalyov Thomas Stringer Kilian Valkhof Vasiliy Emmanuel Pilande Brian Vanderbusch Dave Jeffery tsemerad Daniel Bushman Artyom Kozhemiakin

Something wrong with this page? Make a suggestion

Last synced: 2018-11-28 20:24:38 UTC

Login to resync this repository