Cody A. Taylor

Correct. This is not a show stopper. Just would be a very nice to have for better type support.

(note, I am not a maintainer) I really doubt the issue is with `decompress` not returning a promise. The library always returns a promise, and file writing happens within an...

Some other options: * [merge2](https://github.com/teambition/merge2) (also listed on npmjs.com as "gulp-merge"). * [combined-stream](https://github.com/felixge/node-combined-stream) or [combined-stream2](https://github.com/joepie91/node-combined-stream2). I've personally used combined-stream, but also wonder if I should use something else.

How about suggesting [gulp-noop](https://www.npmjs.com/package/gulp-noop) ([github](https://github.com/eisbehr-/gulp-noop))? Personally I'd prefer that a PassThrough stream was used directly, but I suppose it is implementation details.

I am a bit confused by the suggestion to replace `gutil.buffer` with [`list-stream`](https://www.npmjs.com/package/list-stream). Seems like the more well known [`bl`](https://www.npmjs.com/package/bl) or [`concat-stream`](https://www.npmjs.com/package/concat-stream) would be more applicable. Edit: Oh, I guess...

@katekourbatova You are reading this issue incorrectly. This is about improving suggestions for changing plugins _using_ gulp-util. The case you are displaying is that gulp-decompress needs to follow this advice....

@katekourbatova In fact, it looks like `gatsby-plugin-sharp@next` solves your issue (though for some reason npm install is still showing the gulp-util deprecation notice, not sure why).

> Would you be willing to submit a PR? Sure thing. Wanted to make sure I was at least strolling down the right avenue 😀

PR #1094 was merged. Closing.

The point of this exercise is to understand that `for (var i = 0; i < urls.length; i++) {` is a **sync** control flow tool. The _work_ you are doing...