To me, they serve different purposes. Gulp manages a set of tasks, but is pretty ignorant of what those tasks actually entail. Webpack provides the "guts" of one type of task, specifically preparing source code for use on the web.
Crutchfield uses Gulp to manage build tasks, because it integrates well with Visual Studio. But we launch Webpack in a Gulp task to actually build our JS assets.
Made complex JSON inspecting super easy. Created revolutionary free online tool(https://jsongrid.com) to visualize JSON as table and Connected every table cell to JSON element, awesome right!
Made complex JSON inspecting super easy. Created revolutionary free online tool(https://jsongrid.com) to visualize JSON as table and Connected every table cell to JSON element, awesome right!
Made complex JSON inspecting super easy. Created revolutionary free online tool(https://jsongrid.com) to visualize JSON as table and Connected every table cell to JSON element, awesome right!
To me, they serve different purposes. Gulp manages a set of tasks, but is pretty ignorant of what those tasks actually entail. Webpack provides the "guts" of one type of task, specifically preparing source code for use on the web.
Crutchfield uses Gulp to manage build tasks, because it integrates well with Visual Studio. But we launch Webpack in a Gulp task to actually build our JS assets.
Got it, so Gulp seems like more of generic tool to deal with any kind of task whereas Webpack is specific to web-project.
Pretty much. I'll add the caveat that Webpack can compile to targets besides the web. But it's still basically a compiler.
Ohh! Could please elaborate this little: "Webpack can compile to targets besides the web". Thanks for your response. :)
Sure! The target is specified in Webpack's config (just a JSON object full of settings). There are a number of target options, but the two I'm familiar with are
webandnode.webbuilds JS to be served to web browsers.nodebuilds JS to run on a server with the nodejs runtime.This is good information. I'll definitely look into this. Thanks for this. :)