Doesn't work with --watch about webpackmonitor

[mbehzad]

Hi @DimitarNestorov, you are right, webpack monitor is not ment to be used in a watch mode:
(from #48):

Typically you'd insert webpack monitor as a plugin on your production config and only periodically launch the dashboard.

and the reason being:

the idea being that we are not so concerned about the state of the non-optimized dev builds

That's why on each run a new express instance is started and when the old one blocks the port, an error is trown.
You could set the launch flag to false, or move this to your production webpack config.
maybe webpack monitor will support this one day.
you can also have a look at some similar issues:
EADDRINUSE on compile #48
Support for hot reloading #69
throw error on port 8081 when editing code #78

[DimitarNestorov]

I am going to use webpack monitor to focus on optimizing the production build.
My issue as that if I don't use watch mode I have to wait 5+ mins between each build in order to see the result.
In order to achieve the result I want right now I will use capture: true, --watch and run the webpack monitor express instance without launch: true in the webpack config.

So the ideal situation is capture and launch both to be true and the webpack watcher not to crash.

And auto reload (but I will do it myself using BrowserSyncPlugin [proxy: 'http://localhost:8081/'])

[mbehzad]

@DimitarNestorov , you said supporting a watch mode would be your feature request. What would be your use case, or what behavior would you expect?

• with the current default behavior, when the capture flag in on, then each small change would result to a new point in the chart and the stats would be bloated pretty fast.
• capture: false would allow a stats server to run and show the captured stats, but local changes would not be visualized in the charts.
• another option would be to not capture the changes and save in the stats.json. but to show the current snapshot as the last point in the charts to be compared with captured data.

[DanielRuf]

So the ideal situation is capture and launch both to be true and the webpack watcher not to crash.

Definitely. This is what I expected.

[DanielRuf]

It still says

A tool for monitoring webpack optimization metrics through the development process