Answer the question
In order to leave comments, you need to log in
Why is webpack better than gulp/grunt?
I’m browsing the Internet and more and more often I stumble upon the fact that webpack is forcing. I looked through, looked and figured that I can’t understand why this thing also appeared if there is already gulp? how is it better?
Answer the question
In order to leave comments, you need to log in
Webpack is a build system with tons of features. In particular, it parses JS code (as well as CSS or other, through loaders), this gives it superpowers.
Gulp/grunt is a general system for organizing tasks, which does not itself support assembly, but it can be written on it using plugins. At the same time, there will most likely be no code analysis, which means that a number of advanced features will disappear.
I mean, they are two different things. As one of the tasks on gulp / grunt, the webpack build may well be, and this is usually done.
It is quite possible to write a simple assembly on gulp/grunt directly. And if it’s more complicated or you just want to have a reserve “for the future”, then you can use a special tool (Webpack).
PS I used to have both gulp task assemblers and browserify, but Webpack has taken their place a long time ago.
Cooling theme.
Someone will come.
Personally, I don't like working with styles.
I'd rather do it the old fashioned way through gulp.
// EDIT July 2016
webpack is amazing
happened to collide with webpack .... the assembly went on for 40 seconds, tin tin
And now add npm scripts to all this)
.. some manifesto against the use of gulp, webpack, grunt, etc.
prgssr.ru/development/pochemu-npm-skripty.html
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question