I have been working on developing a gulp plugin that counts the number of files in the stream. Taking inspiration from a helpful thread on Stack Overflow (source), I started implementing the following code:
function count() {
var count = 0;
function countFiles(data) {
count++;
// following official documentation:
this.queue(data);
}
function endStream() {
console.log(count + " files processed");
// Instead of ending the chain like the original post, I am using the following as per the docs:
this.queue(null);
}
return through(countFiles, endStream);
}
module.exports = count;
Furthermore, here is an example task utilizing the plugin:
gulp.task("mytask", function () {
gulp
.src("...files...")
.pipe(count()); // <--- incorporating the plugin here
.pipe(changed("./some/path"))
.pipe(uglify())
.pipe(rename({ extname: ".min.js" }))
.pipe(gulp.dest(./some/path))
.pipe(count()); // <--- another usage of the plugin
});
The functionality works accurately, albeit not starting or finishing as anticipated:
[14:39:12] Using gulpfile c:\foo\bar\baz\gulpfile.js
[14:39:12] Starting 'mytask'...
[14:39:12] Finished 'mytask' after 9.74 ms
9 files processed
5 files processed
This behavior suggests an asynchronous execution that concludes after the task finishes. The documentation recommends either using a callback or returning a stream, which seems to be implemented here.
How can I rectify this issue with the function's behavior? Could it be caused by my use of through instead of the through2 plugin?