Went through this exact process last week. Did they really need to remove CommonsChunkPlugin? Feels like breaking stuff for a slightly nicer API. If this were React we would've had a deprecation warning for a few versions.
> If this were React we would've had a deprecation warning for a few versions.
If this were React, you would have got docs with a release.
Choosing to release before documentation is done, for a tool developers are supposed to use as a black box, which has a lot of strange configuration that is required, is a really strange choice for something with so many breaking changes.
They have [0][1] ("beta" was dropped from the v4 releases at v4.0.0), and are actually in the process of updating the documentation [2]. It's just odd to do that after a release.
Whoops, guess it's a good idea to check things before blurting something out.
In that case I'm not sure what's best, to let newcomers in on the new goodies of v4 or to avoid confusing previous users.
If this were React, you would have got docs with a release.
Choosing to release before documentation is done, for a tool developers are supposed to use as a black box, which has a lot of strange configuration that is required, is a really strange choice for something with so many breaking changes.