Readme needs a comparison with webpack-assets-manifest plugin and others

[nskazki]

I request a comparison between plugins produce files that link asset names to paths. I already knew two others: https://github.com/unindented/stats-webpack-plugin and https://github.com/webdeveric/webpack-assets-manifest. And now there is three. Help me to make the right choice when I start picking up tools for a next project :)

[ztoben]

Good suggestion, thanks 👍

[rake7h]

+1 for this. I'm confused with other similar plugins. I didn't find any blog or stack overflow for this.

https://www.npmtrends.com/assets-webpack-plugin-vs-webpack-assets-manifest-vs-webpack-manifest-plugin

[nskazki]

In my experience, https://github.com/webdeveric/webpack-assets-manifest works great with webpack@4 but glitches with webpack@5. In particular, it replaces paths to bundles with paths to hot-update chunks whenever any are generated. Of course, it isn't a problem if you stick to live-reload but I use HMR, so it doesn't work for me. So, I've replaced it with https://github.com/shellscape/webpack-manifest-plugin and I'm completely satisfied with the result... And yeah, neither of the packages I've mentioned are related to this repo, I just wanted to share my experience xD

[webdeveric]

@nskazki If you have reproducible issues with my plugin (webpack-assets-manifest), please report the issue and I'll take a look.

[hinell]

I think this plugin should be deprecated in favor of webpack-manifest-plugin for webpack v5 and above.