electron-redux

Keeps your state in sync across all of your Electron processes by playing your actions across all of them.

Differences with @mckayla/electron-redux

• Updated dependencies
• Added preload typedefs
• Messed around with the build chain / tooling a bit - now a bit easier to see what is going on and uses PNPM instead of Yarn.
• E2E is more of a modern real-world case utilising React.

This was forked in order to better test electron-redux in an environment similar to an app I am building - I was having issues integrating it with a combination of Redux Toolkit, React-Redux and Redux-Offline. However after much shenanigans the issue was fixed by removing Redux Dev Tools - anyone having issues with this library syncing stores should try removing the Dev Tools in the first instance.

Usage

// in the main process
import { syncMain } from '@goosewobbler/electron-redux';
const store = createStore(reducer, syncMain);

// in the renderer processes
import { syncRenderer } from '@goosewobbler/electron-redux';
const store = createStore(reducer, syncRenderer);

// in your preload script
import '@goosewobbler/electron-redux/preload';

If you don't have your own preload script, you can specify the provided preload script directly whenever you initialize a BrowserWindow

// when initializing a BrowserWindow
const view = new BrowserWindow({
  webPreferences: {
    preload: require.resolve('@goosewobbler/electron-redux/preload'),
  },
});

w/ Webpack

If you use Webpack to bundle your renderer code, and you don't have nodeIntegration enabled, you might also need to prevent the electron module from being included in your renderer bundle. You can do this by including the following in your Webpack config.

// in your webpack.config.js
module.exports = {
  resolve: {
    alias: {
      electron: false,
    },
  },
};

w/ Parcel (or Webpack)

In your renderer code, you'll actually want to import the store enhancer from a submodule.

// in your renderer processes
import { syncRenderer } from '@goosewobbler/electron-redux/renderer';
const store = createStore(reducer, syncRenderer);

Actions

Actions MUST be FSA-compliant, i.e. have a type and payload property. Any actions not passing this test will be ignored and simply passed through to the next middleware.

NB: redux-thunk is not FSA-compliant out of the box, but can still produce compatible actions once the async action fires.

Actions MUST be serializable

• Objects with enumerable properties
• Arrays
• Numbers
• Booleans
• Strings
• Maps
• Sets

Local actions

By default, all actions are played in all processes. If an action should only be played in the current thread, then you can set the scope meta property to local.

const myLocalActionCreator = () => ({
  type: 'MY_ACTION',
  payload: 123,
  meta: {
    scope: 'local', // only play the action locally
  },
});

We also provide a utility function for this

import { stopForwarding } from '@goosewobbler/electron-redux';
dispatch(stopForwarding(action));

Contributors

• Mckayla Washburn
• Burkhard Reffeling
• Charlie Hess
• Roman Paradeev