4 ms·
Maybe I'm the crazy one here, but giving plugin authors a single month to get updates out to support webpack 4 was a really irresponsible way of releasing this.
by karmajunkie 9y ago
Maybe I'm the crazy one here, but giving plugin authors a single month to get updates out to support webpack 4 was a really irresponsible way of releasing this. When people kvetch about what a shitshow the javascript scene is, this is exactly the kind of thing they're talking about.
- exogen 9y agoWhat are you even talking about? It's a semver-MAJOR release. Nobody is going to accidentally upgrade to 4 and have everything break, unless they are very confused and cavalier with bumping their dependencies. So people relying on old plugins can just stick with webpack 3 which works perfectly fine. I'm not a webpack contributor, but I'd rather get a new version into everyone's hands sooner rather than wait for random third-party developers not associated with the project to get their stuff in order.
- karmajunkie 9y agoIts not a matter of whether someone accidentally upgrades to a major release. Its a matter of whether the release is ready to use in production, and when you have plugins like extract-text that are crucial components to the vast majority of workflows and they haven't been given enough time to upgrade, you can't seriously claim that v4 is production ready. If its a matter of putting it in the hands of users sooner than later, that's what a beta period is for. Releasing this before the documentation is even ready is just irresponsible.