Gulp.js
A toolkit to automate & enhance your workflow. Leverage gulp and the flexibility of JavaScript to automate slow, repetitive workflows and compose them into efficient build pipelines.
Features
- Extensible by Plugins/Extensions
- Workflow Automation
- Support for Typescript
Tags
Gulp.js News & Activities
Recent News
Recent activities
Gulp.js information
Developed by
FractalLicensing
Open Source (MIT) and Free product.Written in
Alternatives
13 alternatives listedSupported Languages
- English
AlternativeTo Category
DevelopmentGitHub repository
- 33,033 Stars
- 4,199 Forks
- 34 Open Issues
- Updated
Featured in Lists
Master List of all Apps and Software I use for both work and personal life.
A list with 809 apps by AmileyaRyver without a description.
Here is a non-exhaustive list of the tools I use for developing websites.
What is Gulp.js?
A toolkit to automate & enhance your workflow. Leverage gulp and the flexibility of JavaScript to automate slow, repetitive workflows and compose them into efficient build pipelines.
- Flexible: Using code over configuration, utilize all of JavaScript to create your gulpfile—where tasks can be written using your own code or chained single purpose plugins.
- Composable: Write individual, focused tasks and compose them into larger operations, providing you with speed and accuracy while reducing repetition.
- Efficient: By using gulp streams, you can apply many transformations to your files while in memory before anything is written to the disk—significantly speeding up your build process.
Connecting plugins
Using community-built plugins is a quick way to get started with gulp. Each plugin does a small amount of work, so you can connect them like building blocks. Chain together plugins from a variety of technologies to reach your desired result.
Comments and Reviews
For me, Gulp is much better than Grunt. Simple watch + less + aftoprefixer + minify task on 3-4 files ran about 2.2 seconds on grunt, and almost instantly on gulp (when file is changed and recompiled on-fly) Major problem of grunt is every time it spawns new process and reloads entire config. Yes, you can optimize gruntfile, but it's still much worse than keep it in memory like gulp does. And you can set not to spawn grunt process for certain task, but it will stop entire watch task on errors. There are no gulp-plumber alterative for grunt (tell me if i'm wrong). When you rebuild entire project, it's not big issue, but if you watch for certain files and livereload - big latency between file changes and completion of rebuilding single file is problem. Also, gulp uses pipes, so each file processing can be done in memory, only final result written on disk. This gives additional performance, 'cause disk operations are slow.