• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• The changes are appropriately documented (if applicable).
• The changes have sufficient test coverage (if applicable).
• The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:

Summarize your changes:

Note that this replaces #2856 based on this suggestion.

We have multiple BrowserWindows in our project, some which use nodeIntegration: false and some which use nodeIntegration: true.

Without this change we get the error require is not defined at runtime in the BrowserWindows with nodeIntegration: false.

We didn't need to do this with older versions of @electron-forge/plugin-webpack that used Webpack 4 where we could simply not import any Node JS modules and just use browser-targeted modules.

@electron-forge/plugin-webpack only allows us to set one target for all entrypoints. This change allows overriding the nodeIntegration value for a specific entrypoint. e.g.

  plugins: [
    [
      '@electron-forge/plugin-webpack',
      {
        mainConfig: './webpack.main.config.js',
        renderer: {
          config: './webpack.renderer.config.js',
          nodeIntegration: true, // Implies `target: 'electron-renderer'` for all entrypoints
          entryPoints: [
            {
              html: './src/app/app.html',
              js: './src/app/app.tsx',
              name: 'app'
            },
            {
              html: './src/mediaPlayer/index.html',
              js: './src/mediaPlayer/index.tsx',
              name: 'media_player',
              nodeIntegration: false
            }
          ]
        }
      ]
    ]

This uses Webpack's ability to pass an array of webpack configurations rather than a single configuration.