Gulp is a JavaScript build system, Node.js-based task runner like Grunt. Gulp uses streams and code-over-configuration for a simpler and more intuitive build process.

- Wiki
9 articles, 0 books.

A build tool automates the time-consuming, repetitive tasks in our workflow so we don’t have to do them manually.

When you use gulp as your task runner as is common in JavaScript development these days, your gulpfile.js contains a series of tasks. Some of those tasks might depend on each other so that a certain execution order has to be ensured. After all, you don't want to clean a directory right after you've written files to it.

Gulp is a tool that helps you out with several tasks when it comes to web development.

In Visual Studio, a Task Runner contains collection of "tasks" that can be executed either on demand, or automated as part of a build process. Visual Studio includes native support for Grunt.js and Gulp.js task runners, and each of these is designed to make building client-side resources easier.

I know what you’re thinking. WAT?! Didn’t Gulp just kill Grunt? Why can’t we just be content for a few minutes here in JavaScript land? I hear ya, but…

Would it be possible to wire node.js and Gulp with ASP.NET in my existing web project? It turns out you can. Although, at this point, it isn’t as straightforward as most other things in Visual Studio.

This post is going to cover taking a project that is using Bundler & Minifier and change it to use gulp instead.

Every project has its environment. Switching between projects means switching environments. Switching environments means remembering commands for running project tasks, like Gulp or webpack. But too often commands are forgotten.