documentation - install - setup - why
features
- gulp API and more
- customizable logging
- REPL with autocomplete
- Tasks :names with :parameters
- pass arguments from the task runner
samples
CLI as tasks
var gulp = ; gulp;
task :parameters
var gulp = ; gulp; gulp;
passing arguments
var gulp = ; gulp; gulp; // the default takes any arguments after '--' from the terminalgulp;
write
node gulplfilejs -- src/**/*js build
and arguments after --
will be passed to the default
task.
functions as tasks
Just as gulp#4.0
var gulp = ; { console; return gulp // some build step ;} { return gulp // minify ;} gulp;
split builds in instances
var styles = ; styles; styles; exports = moduleexports = styles;
default
has finished
a REPL after var gulp = ; gulp; gulp;
go to the terminal and do
node gulpfile.js
which will run a REPL with the tasks defined.
install
With npm
npm install --save-dev gulp-runtime
why
Soon after I started to use gulp
it came to mind
I want a REPL for this
Mainly because a REPL is the closest to define and use as you like
. If that was possible then writing task names in this REPL will run them just as doing the same from the command line.
Then I realized that what I really liked from gulp
is the way you can bundle and compose async functions and how its this done under the hood. For that I had to try to do it by myself.
The above has lead to gulp-repl, parth, runtime and finally gulp-runtime.
So yeah, it got out of hand :D.
But well oh well, here we are.