4 ms·
Hello. Webpack team member here. The webpack@4 release was, well, interesting. I can't add much that hasn't already been said - but I can say that we're working
by andrew_ 9y ago
Hello. Webpack team member here. The webpack@4 release was, well, interesting. I can't add much that hasn't already been said - but I can say that we're working to make sure there will never be another webpack release that suffers from the same kind of documentation shortcomings. There's a metric poopton of good stuff in the release, and we're still working to get all of it written down. That said, look for future major releases to be far more proactive than reactive with regard to documentation, announcements, and migration details.
- ggregoire 9y agoHey Andrew, thanks for the great work on v4. Webpack is one of these tools I can't imagine working without.
- tbrock 9y agoHey thanks for all the hard work! > I can say that we're working to make sure there will never be another webpack release that suffers from the same kind of documentation shortcoming We still have time to make sure this release has good docs. Please don’t give up on it just yet! Can we make some task issues on github that ask people to document a portion of the code/process?
- shakna 9y agoHave a look at this issue [0], I think it covers most of the docs for v4. [0] https://github.com/webpack/webpack.js.org/issues/1861 https://github.com/webpack/webpack.js.org/issues/1861
- chvid 9y agoI upgraded my projects to webpack 4 about a month back and I did not have much of an issue. The builds are definately faster. I would say this though: Webpack (and in general the current JavaScript-way of building) is one of those build systems that invite programmers to put a lot of stuff into their project builds plus a lot of programmers rely on templates or generators that gives a lot of code that they never bother to understand. That is a recipe for stuff that is hard to upgrade and hard to maintain.