use AutoDllPlugin to separately build vendor dependencies?

[agilgur5]

https://github.com/asfktz/autodll-webpack-plugin is a significantly simplified plugin that combines the standard DllPlugin + DllReferencePlugin into one.

The README says it will be obsolete with webpack 5's built-in caching, but there isn't a timeline for that and I'm not sure what types of caching it will include, since HardSourceWebpackPlugin, DLL, and others don't completely overlap with each other. HardSource seems like it will be fundamental to webpack 5, but not sure about DLLs. mzgoddard/hard-source-webpack-plugin#251 (comment) shows that the two are complimentary: while HardSource makes the largest benefit, DLL can speed up production builds -- but actually slows down dev builds when used with HardSource.
DLL can also be used similarly to a vendor / commons chunk in production, but chunking might make more sense / be more predictable for use in production, though chunking doesn't cache builds, so DLL is still better for prod build perf (unsure if HardSource w/ CommonsChunk for prod builds would make DLL obsolete for prod as well). https://stackoverflow.com/questions/41890855/webpack-common-chunks-plugin-vs-webpack-dll-plugin goes into how they achieve similar goals

Other things to consider as well:

1. Configuring modules to be included: Automatically building the dependencies list asfktz/autodll-webpack-plugin#54
2. There are quite a bit of open issues that seem like they could cause quite a bit of bugs