feat: add stats option to webpack plugin

[depoulo]

Summary

Fix #770 as per my suggestion.

Test plan

1. Use plugin as before. Output should be identical.
2. Use plugin while passing custom stats options. The generated stats JSON file matches those options.

[tomkelsey]

Hey,

I've read the related conversation to this PR and saw (#770 (comment)) you say perhaps this was overkill and that #779 would suffice.

Personally, I re-use the assets json file for a few other bits and bobs and so the most recent update to loadable-components broke my setup. I've had to patch the code to add in an extra stats option (namely entrypoints) so this PR - allowing people to customise the stats options - would still be valuable for my use case 👍

[depoulo]

Good point. While we're waiting for a maintainer's opinion on this, feel free to use

"@loadable/webpack-plugin": "depoulo/loadable-components#@loadable/webpack-plugin/stats-opts-770/5.16.0",

in your package.json in the meantime (still better than patching the code).

[theKashey]

Actually I always thought about splitting plugin into two parts - Webpack and stats.

you should not use plugin output for anything except loadable itself, please try to learn from this incident...
But nothing is stopping loadable to derive stats it needs from “your stats”

that automatically “grants” you ability to use any plugin you want and decouples loadable server from Webpack integration.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.