Takayuki Sato
Takayuki Sato
@phated Does what your changes suggest that if a config file in `initCwd` has `flags.gulpfile` or `flags.cwd`, `gulp-cli` should change cwd to `env.cwd` and then loads `.gulp.*` file in the...
If so, I have two ideas to fix this issue: (The following codes are not actual but an example.) 1. Process a config file in `initCwd` before `cli.prepare`. ```js var...
> I'm wondering if we shouldn't move https://github.com/js-cli/js-liftoff/blob/master/index.js#L62-L111 into the execute phase. Rather, that moving may be necessary because there is a case that gulp cannot be run only by...
Furthermore, the current gulp with `--cwd` option loads and processes `.gulp.*` in the chaged directory. I think this behavior is correct, but to reproduce the same behavior with a config...
Yes, I'll address this weekend.
@KleptoKat I suppose your aim in this issue is to make enable to run post-tasks of a watch task and finish them normally by gulp-cli when CTRL+C is entered. And...
@phated Should we implement the solution for this issue? The solution would be like the following: ``` const gulp = require('gulp') // 1) Override the current `watch` function const origWatch...
I think it's correct to regard all arguments after `--` as non-options. `--` is a special argument marking the end of options. This behavior is due to **yargs** and follows...
I have considered before about task's flags to make naming spec., for example: ``` $ gulp task1 --task1:flag1 value1 --task1:flag2=value2 --task1:flag3,flag4=value4 --- (gulpfile.js) gulp.task('task1', (cb, {flag1, flag2, flag3, flag4}) =>...