gulp vs. Brunch

The go-to processor. Throw in any npm-lib, win.

I use gulp to do repetitive tasks and optimize css and js.

All the Front-end is pre-processed/merged/minified/modularized for production usage using gulp.

Gulp builds the Angular front-end

File versioning, compilation, minification, etc...

I use gulp to power my build/minification flow, as well as for running a local livereload webserver while coding.

Front-end builds: producing full minified css/js output from a series of css/less/coffee/cjsx/js components.

Switched from grunt and haven't looked back. Like using standard npm libs instead of relying on a grunt-specific plugin.

As the main frontend build tool, covering:

• bower dependency injection
• deployment methods
• build versions i.e. dist, local server etc.

For all our frontend site builds, Grunt allows us to do one-click builds for SASS, Coffeescript and other tools, with minifying and general restructuring built right in.

Gulp is our build tool and also helps in development with live-reload using gulp-connect and watch.

Compile stylesheets and work with browserify to wire up dependencies and optimize front-end application code.

Build automation for front-end web client.

I prefer gulp to grunt.

As a tool to run linter, unit tests, changelog on the voiceping node.js backend

Gulp is used as the build system for Cloudcraft.co with a lot of custom targets: vendoring dependencies, transpiling ES2015 to Ecmascript5 (with Babel), incremental compilation of multiple watched modules, minification, creation of app distribution packages etc. Having previously used Grunt, I've come to greatly prefer Gulp due to the ability to easily write my own tasks using plain JS without necessarily relying on plugins for everything.

We used Gulp in each frontend and Node.js project to automate development & build tasks

Web development site setup

With Gulp we managed development tasks using plugins, as eslint, jscs, uglify and Browserify.

Gulp is used for writing transpiling, bundling, minification, watching and other tasks.

Automate all things build related with the client single page app

Building our frontend app

Currently minimizes CSS and JS. Runs Java Script code inspections.

Vulcanize Polymer elements

Gulp is our build tool of choice for the Giant Swarm web user interface

Gulp is used to configure build pipeline, from jekyll build command to minification, cleaning and optimization of static assets (js,css, img).

To run the tasks required during development (SCSS compilation, image minification, JS concatenation & minification).

build assets and optimisation

It gulps things for me. I.e., it does all the work that I'm too lazy to do.

Frontend build script

If a project has a more complex build, gulp allows us to build a flexible build pipeline and automatically rebuild on files changes. Speeds up JS development.

Great Build tool for complex Web App.

JS Build tool

use for my front-end build needs. very powerful, lots of great plugins. makes development and the feedback cycle blissful.

Automate task

프론트엔드 빌드 태스크는 gulp를 통해 관리 및 자동화 수행을 합니다.

Lovely, like it a lot, tasks/streams resonates with my way of thinking

Development workflow, SASS compilation.

gulp is used to package our plugins for the WSC (Woltlab Suite Core) in a fast, convenient and code-driven way. We enjoy the comfort it offers with stuff like the gzip-plugin or tar-packing.

Easy to configure with plenty of addon modules available.

Gulp is amazing! Make for your web stack! You can do anything with it!

Moving from gruntjs to gulpjs was a nice option, coding over setting was a game changer to me. Flexibility in my builds.

Makes use of pre-processors very easy. It can build most of the popular templating tools.

gulp is a fancy alternative to grunt (that we don't use anymore). Just use async/await instead of "stream" everything (which is a nonsens). We don't use gulp.

PrometheanTV utilizes the Gulp tool in the Broadcast Center Tool build pipeline.

compiling web assets