3 ms·
I don't want to be a naysayer. But the premise of the title is that Webpack is the current big thing. And I read the whole article and don't really understand w
by texaslonghorn5 4y ago
I don't want to be a naysayer. But the premise of the title is that Webpack is the current big thing. And I read the whole article and don't really understand why Webpack is the current big thing. The whole JavaScript ecosystem seems very disjoint and although I'm not immersed in it, I figured I would have heard of Webpack before or at least seen it on this site if it was so big. I have heard of npm and Babel before, but maybe that's just good marketing (or maybe I just missed a whole generation?).
- jdlshore 4y agoYou’re just out of loop. Webpack is the current big thing. It rose to prominence after grunt and gulp, which were both build automation tools. Webpack supplanted them by being a “one stop shop” for many of the things grunt and gulp were used for. However, as always happens, that convenience spiraled into increasing complexity as people wanted more and more out of their builds.
- MrBoomixer 4y agoI would agree with this statement. You may not see Webpack directly because a lot of modern tooling/libraries/frameworks (whatever we're calling them now) have Webpack hidden away in their dependencies and the end consumer gets a hand full of useful cli commands that run magic.