Closed apowers313 closed 5 years ago
You really really really don't want to combine different types of asynchronousity like that. You'd be opening yourself to a world of bugs and other issues.
If you want to do this in gulp, just keep it simple:
let config;
async function setup() {
config = await someSetup();
}
const myTask = gulp.series(setup, function() {
return gulp.src(/*...*/).pipe(/*...*/);
});
Would it be acceptable to have async-done wait on a Stream or a ChildProcess that is the result of a resolved promise?
Use case is like this:
Happy to submit a PR if this is a good idea.