[webpack] allow specifying watch options for the dev server

[farfromrefug]

On my computer i have some issue with electron-forge which uses all my cpu on start with wepback.

I think it's related to webpack watch feature.
To "improve" the situation i added options to the dev server [here] (https://github.com/electron-userland/electron-forge/blob/master/packages/plugin/webpack/src/WebpackPlugin.ts#L280)
Adding (doc):

watchOptions:{
     aggregateTimeout: 500,
      poll:1000,
      ignored: /node_modules/
 }

made the CPU usage go down to 50%. Which is much better (though still not that good).

Could you add a way to pass options to the dev server through the webpack plugin configuration?

Thanks

[sirgallifrey]

I want to help with that, I just think we should figure out how to test the webpack plugin first, see #639

[delewis13]

Bump to this issue.

It seems to be a pretty serious shortcoming. The manual fix to WebpackPlugin.ts [including watcherOptions] also solved my CPU issue.

In my case, I am writing a mid-sized React based app, and noticed electron-forge-start.ts was destroying my CPU.
Prior to change -> idle at 200% CPU.
Post change -> idle at 5% CPU

Using boiler plate from docs, electron-forge-start.js was using 5% of CPU while idling. After change it uses 1%.

So it seems that the CPU used scales with project size, and that the problem is only further exacerbated as project grows.

[delewis13]

Bump again on this issue. Fix seems simple, have had to apply this patch at least 8 times in the past month due to package updates / overwrites / reinstalls of node_modules on various dev machines.

Is there any reason to just include these watch options in the default watcher config?