Rebuiltron

A tool made to easily build an offline React/Electron app using webpack.

---

Why

The idea behind Rebuiltron was to migrate one of my project initially created with the deprecated CRA to a maintained tool configured with Electron in mind. As such, it has been developed using react-scripts as a base, but heavily edited and stripped of a lot of features.

Important

Since I made Rebuiltron specifically for one of my own projects, I only kept in the configuration what this project needed and nothing more. For this reason, Rebuiltron doesn't offer many configurable options. If you are looking to create a new Electron/React app, or even migrating an existing CRA app, you should probably look for a more generic tool.

Features

Rebuiltron uses webpack with SWC to compile JavaScript instead of Babel.

• Support for multiple windows and preloads
• Development server taking care of starting Electron
• Production bundler for React and Electron code
• Support for React, JSX, SASS, ICSS
• Support for ES6 imports on all processes

Warning

Rebuiltron doesn't support: TypeScript, Flow, CSS Modules, ESM, and proxying.

Installation

yarn add rebuiltron -D

React and Electron are required dependencies you must install separately.

Configuration

The following documentation assumes you already have a basic knowledge of how to use React and Electron.

Folder structure

Rebuiltron expects the following folder structure:

my-app
├── public/
│   └── # Renderer HTML file(s)
├── src/
│   └── # Renderer JS file(s)
└── package.json

Main entry

Set the main Electron entry in package.json:

{
  "main": "build/static/js/electron.main.js",
}

This field points to the compiled version of the main file and must be named as above. Your original main file can be named however you want.

Scripts

Add Rebuiltron scripts to your package.json:

{
  "start": "rebuiltron start",
  "build": "rebuiltron build",
}

The build command will bundle your code so it's ready for production, but it will not package it into a working app. For this task, you need to use a tool such as Electron Forge or electron-builder.

Browserslist

Add your desired browserslist in package.json:

{
  "browserslist": "last 2 electron major versions",
}

Configuration file

At the root of your project, create a rebuiltron.config.js file.

Options:

Name	Type	Required	Description
main	string	✓	Main entry. The path must be relative.
renderers	object	✓	Renderer entries. It takes the name of the entries as keys and their paths as values. All paths must be relative.
preloads	object	✓	Preload entries. It takes the name of the entries as keys and their paths as values. All paths must be relative.
srcAlias	string	✗	Custom alias to the src folder.
excludeInProduction	string[]	✗	List of modules to exclude in the production bundle.
sassOptions	object	✗	Custom SASS options for sass-loader.
sassOptions.additionalData	object	✗*	Configuration of additionalData.
sassOptions.additionalData.data	string	✗*	Data to prepend to SASS files.
sassOptions.additionalData.exclude	Regex	✗*	Regex matching the files to exclude from additionalData. This is necessary to prevent an @import loop error.

^{*Required when sassOptions is defined.}

Example:

module.exports = {
  main: "./electron/main.js",
  renderers: {
    app: "./src/app.js",
    worker: "./src/worker.js"
  },
  preloads: {
    app: "./electron/preloads/app.js"
  },
  srcAlias: "@app",
  sassOptions: {
    additionalData: {
      data: "@use \"styles/settings\" as *;",
      exclude: /^src\\styles\\.*/
    }
  },
  excludeInProduction: [
    "electron-devtools-installer"
  ]
};

Note

Your renderers entry file(s) will be automatically injected into your HTML file(s). Thus, make sure you have a corresponding HTML file in the public folder for each entry (using the same name).

Preloads

Since Rebuiltron will build the preload file(s) both in development and production, you can use a single path for both environment. Built files use the names declared in your configuration: electron.preload.[name].js.

const appWindow = new BrowserWindow({
  webPreferences: {
    // Using the example configuration file above
    preload: path.join(__dirname, "electron.preload.app.js"),
  }
});

Environment variables

When the development server is running, Rebuiltron exposes a DEV_LOCAL_URL variable that you can access on your main process using process.env.DEV_LOCAL_URL.

app.isPackaged
  ? appWindow.loadFile(join(__dirname, "../../app.html")) // Prod
  : appWindow.loadURL(`${process.env.DEV_LOCAL_URL}/app.html`); // Dev

Usage

To run the development server:

yarn start

To create the production build:

yarn build

Contributing and feature requests

I made Rebuiltron specifically for a project of mine, and for that reason, I have no plans to add new features nor to accept contributions, unless required for this project in particular. If you wish to use Rebuiltron but need something that is not available in the current configuration, please feel free to create a fork and change the code to your needs.

License

MIT