BUG: Handle large webpack stats bundles without socket.io client disconnect.

[ryan-roemer]

Current Notes

Thanks to great insight by @westbrook-asapp it appears we're sending the full webpack stats object from client (webpack plugin) to server (CLI) when we only need the errors and warnings fields. This PR:

• Limits the webpack stats messaged object to just errors and warnings. Fixes BUG: Large webpack stats bundles cause socket.io client disconnect. #279
• Add client disconnect / error messages to help analogous issues in the future.

/cc @parkerziegler @westbrook-asapp

Old, WIP debugging info

Currently can reproduce the bug in #279 as follows:

$ yarn

# Run normally. => NO DISCONNECT MESSAGE / WORKS
$ cross-env EXAMPLE=simple node bin/webpack-dashboard.js -- webpack-cli --config examples/config/webpack.config.js --watch

# Run with hack to inject a **huge** source payload. => "Socket.io disconnected. Possibly build data too large?"
$ cross-env EXAMPLE=simple TMP_BIG_STATS=true node bin/webpack-dashboard.js -- webpack-cli --config examples/config/webpack.config.js --watch

I haven't started at looking at solutions, but we've easily now captured the error with the large payload size from @westbrook-asapp . I've even attempted to further refine the "bad" threshold in code, although that may well be machine dependent?

I think next step is see if there is some issue in socket.io that has potential solutions (either in client or server) or something else...

[ryan-roemer]

@parkerziegler -- This is unrelated but useful so I can use https://github.com/FormidableLabs/lank#readme when working on both inspectpack and webpack-dashboard at the same time...

[parkerziegler]

Yep, I remember looking at lank for symlinking, all good here!

[parkerziegler]

Yep, I remember looking at lank for symlinking, all good here!

[parkerziegler]

Nice, thanks for including this here!