|Hacker News, Reddit, Stack Overflow Stats|
|Why people like using this service||
|Companies using this service|
May 05, 2016 20:39
love it！l like gulp‘s logo！
Streamline your build system
May 29, 2014 21:15
Gulp is a new build system which shows a lot of promise. The use of streams and code-over-configuration makes for a simpler and more intuitive build. There isn't much boilerplate code so you're able to roll your own asset pipeline. Even if you don't know node.js streams, gulp is pretty readable and easier to understand.
PS: It's worth saying if you know Grunt then you can learn Gulp in a day.
I will never get those hours of my life back
May 25, 2016 14:36
Grunt is all based on configuration. Some of the configuration is well documented, and some pre-built Gruntfiles can be dropped in and work like a charm. But if you are ever in the position where you have to make any changes to your large and complicated Gruntfile, set aside a few days to work on it. The deeper you get into it, the less intuitive you will find it, and the more strange behaviors you will find from plugins with some 'automagical' undocumented configuration or behavior. If you want a build process that you can understand, and that six months from now you will still understand, you are better off using Gulp.
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.
To run the tasks required during development (SCSS compilation, image minification, JS concatenation & minification).
Gulp is used to configure build pipeline, from jekyll build command to minification, cleaning and optimization of static assets (js,css, img).
With Gulp we managed development tasks using plugins, as eslint, jscs, uglify and Browserify.
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.
Compile stylesheets and work with browserify to wire up dependencies and optimize front-end application code.
Gulp is our build tool and also helps in development with live-reload using gulp-connect and watch.
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.
As the main frontend build tool, covering:
Switched from grunt and haven't looked back. Like using standard npm libs instead of relying on a grunt-specific plugin.
Front-end builds: producing full minified css/js output from a series of css/less/coffee/cjsx/js components.
I use gulp to power my build/minification flow, as well as for running a local livereload webserver while coding.
All the Front-end is pre-processed/merged/minified/modularized for production usage using gulp.
We use it in development for the main application and is responsible for generating the Electron binary artifacts for the client application.
Grunt fills a gap in the Jekyll asset pipeline by augmenting Jekyll. It's used to minify images, concatenate and uglify JS and soon to upload images to an S3 bucket at the
Webpack compiles files to bundles with source maps. Using Webpack you can use the latest features (ES6) and have it compiled to compliant js.
All ES6 was transpiled trough the babel-loader. CSS was prefixed and minified with postcss-loader. Images optimized with imageoptim.
My preferred build tool; allows me to bundle my JSX, JS, CSS files for easy access and I can pass the bundle through my node server for server side rendering.
We use Webpack for packaging across all our applications, which are based on React.js and React Native.