@loopmode/electron-webpack-config-yarn-workspaces v0.2.0

@loopmode/electron-webpack-config-yarn-workspaces

electron-webpack config adjustments for yarn workspaces support.

Usage

Pass the current configuration object to the function and use the modified return value. Always specify the path of the workspace root folder. Optionally specify a libAlias (see below).

// packages/electron-app/webpack.renderer.config.js
const configureYarnWorkspaces = require("electron-webpack-config-yarn-workspaces")
const workspaceRoot = path.resolve(__dirname, "../..")

module.exports = function(config) {
  config = configureYarnWorkspaces(config, workspaceRoot)
  return config
}

Arguments

configureYarnWorkspaces(config:object, root:string, libAlias?:string):object

config

{object} config - the current webpack configuration object.

You get this when you provide a custom electron-webpack config module that exports a function.

root

{string} root - absolute path of the workspace root (required)

This is typically two folder levels up when your file is inside {workspaceFolder}/{packageFolder}.

libAlias

{string} [libAlias] - relative path inside packages to include in alias target (optional)

If your packages transpile to their lib folders, you would normally have to type out that path when importing their modules. When you provide a libAlias: 'lib' option, you can omit the aliased part from the import path:

without libAlias

// in webpack config:
module.exports = function(config) {
  return configureYarnWorkspaces(config, workspaceRoot)
}

// later in code:
import Button from "@my/package/lib/components/Button"

with libAlias

// in webpack config:
module.exports = function(config) {
  return configureYarnWorkspaces(config, workspaceRoot, "lib")
}

// later in code:
import Button from "@my/package/components/Button"

Background

The scenario is a project using yarn workspaces and multiple apps sharing multiple modules. One workspace package is an app built with electron-webpack. Another package is an app built with create-react-app. Any number of additional packages (utils, modules, anything) exist in the workspace, and they are watched and transpiled by some tool (e.g. babel or typescript). Each of those packages gets its src/ folder transpiled to a consumable dist/.

Due to the nature of yarn workspaces, all workspace packages are symlinked into the project root's node_modules folder, and thus available to all other workspace packages.

Problem

The default setup of electron-webpack does not detect changes to files that are outside of its own directory. When the electron-webpack app runs in development mode, and you change the code of some module from a workspace package, the app does not reload the changed modules.

This is because electron-webpack employs a custom WatchFilterPlugin and uses it for ignoring changes to files that aren't part of its app's sources.

Solution

The latest versions of electron-webpack allow us to modify the webpack configuration by providing a custom configuration module that exports a function. That function is invoked with the current webpack config object, and should return a final config object.

The electron-webpack-config-yarn-workspaces solution overrides the filter function and allows files from workspace packages to be watched for changes.