[6.x] Support responding to /sockjs-node/info at webpack dev server

[MOZGIII]

Preflight Checklist

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

I'm using https://github.com/pmmmwh/react-refresh-webpack-plugin and it sends info requests to show compile-time errors. They fail with 404.

Proposed Solution

Add support for presenting compile-time errors.

Alternatives Considered

I considered disabling the info requests on the client. However, this is

• not implemented;
• clearly a worse option.

Additional Information

electron-forge 6 beta 50

[malept]

The main thing blocking this is that we're not currently using webpack-dev-server. This is because we're using a custom logger so that we can send webpack output to the stats webserver. In order to fix this without adding a lot of functionality to Electron Forge itself, we would need to refactor to use webpack-dev-server and also be able to redirect console to the stats server, via logger.configureDefaultLogger({..., console}).

[MOZGIII]

I think part of the problem is this plugin is loaded in the preload entrypoint. Is there a way to only enable a plugin for render non-preload entry points only?

[malept]

Is there a way to only enable a plugin for render non-preload entry points only?

Not currently. The renderer config is loaded into the associated preload entry point's config.

[simonh1000]

Another reason for wanting the webpack-dev-server is for its proxying and before capabilities

[malept]

As of beta 56 the webpack plugin has been refactored to use webpack-dev-server instead of a custom express app.