simpler than gulp-runtime

[stringparser]

This is maybe what I should have done from the beginning with gulp-runtime just a simple module.

I think you'll be interested in this one @DarkPark

[DarkPark]

thanks
will sure take a look
I also have an alternative point of view on the matter
after I think it over I'm going to discuss it with you - you may like it as well :)

[stringparser]

Great 👍

[stringparser]

Know what I just made you collaborator, so do as you see fit ;)

[DarkPark]

thanks :)

[DarkPark]

it works :)

only one minor thing I've noticed - need to press Ctrl+C twice to exit
the package node-static is seems the cause (without this task works fine)
but I remember you've already fixed the similar issue
maybe you can advise something?

[DarkPark]

found it:

var repl = require('gulp-repl');

repl.on('SIGINT', function () {
    process.exit();
});

[stringparser]

Yep, that's it :). If you want to PR and merge it go ahead. Add an exit code though (process.exit(0)).

I've thought to add the ability to run in a task in series/parallel directly from the repl. But not much more aside of whats here. Any ideas?

[DarkPark]

but it's possible to run tasks in parallel
in console I can type:

> img jade less

and I see in logs that they run in parallel

sadly it's impossible to run a task with options

[stringparser]

Yes, gulp runs them in parallel by default. I was talking about this

> series img jade less

Being series a special word for the repl.

With gulp-runtime you can pass options :).

var gulp = require('gulp-runtime').create({repl: true});

gulp.task('jade :glob', function(){
  // do stuff
});

gulp.stack('jade app/**/*.jade')();

Same using the repl

> jade app/**/*.jade

But to do that you have to monkeypatch gulp.task so you can modify how tasks are defined. I would like to keep things simple for this one.

That said, if you find some simple way I'm up to it.

EDIT: that's one of the reasons I had to do all using vinyl-fs directly

[DarkPark]

I see
One more idea - persistent history
using console a log I get used to have a full history of your commands
and in the repl you have it as well but only for the current session
would be cool to save it in a configured file on exit and restore it on start

[stringparser]

Yeah, that would be great. They did this on nodejs/node#1513, I'll take a look on how they did it. In any case it should be behind an option like repl({historyFile: 'some/path/here'}) so it does not surprise anyone when it writes to disk.

[DarkPark]

agree
seems promising

[DarkPark]

one more idea
in case you mistype a task name you get:

[16:53:23] Task 'll' is not in your gulpfile
[16:53:23] Please check the documentation for proper gulpfile formatting

and process exits
would be nice to not halt the programm

[stringparser]

Yep, that's doable. It would be just to check each of the given arguments before running them and see if there is any that is not defined as a task.

[stringparser]

What about not exiting the process at all? I mean, just to mistype a name is not a big deal