[polymer-build] not working with gulp version 4

[opus1269]

I am converting to version 4 of gulp and ran into the following bug:

"C:\Program Files\nodejs\node.exe" C:\Users\mike\Documents\GitHub\screensaver\node_modules\gulp\bin\gulp.js --color --gulpfile C:\Users\mike\Documents\GitHub\screensaver\gulpfile.js prodTest
[18:02:24] Using gulpfile ~\Documents\GitHub\screensaver\gulpfile.js
[18:02:24] Starting 'prodTest'...
[18:02:24] Starting '_poly_build'...
Deleting build/prodTest directory...
Analyzing build dependencies...
[18:02:37] gulp-imagemin: Minified 7 images (saved 25.5 kB - 29.3%)
[18:02:47] '_poly_build' errored after 23 s
[18:02:47] Error: stream.push() after EOF
at readableAddChunk (_stream_readable.js:229:30)
at PassThrough.Readable.push (_stream_readable.js:197:10)
at PassThrough.Transform.push (_stream_transform.js:151:32)
at BuildAnalyzer.dependencyPathAnalyzed (C:\Users\mike\Documents\GitHub\screensaver\node_modules\polymer-build\lib\analyzer.js:426:34)
at Promise (C:\Users\mike\Documents\GitHub\screensaver\node_modules\polymer-build\lib\analyzer.js:484:45)
at Promise ()
at StreamLoader. (C:\Users\mike\Documents\GitHub\screensaver\node_modules\polymer-build\lib\analyzer.js:477:20)
at Generator.next ()
at C:\Users\mike\Documents\GitHub\screensaver\node_modules\polymer-build\lib\analyzer.js:20:71
at Promise ()
[18:02:47] 'prodTest' errored after 23 s

Process finished with exit code 1

What is happening is that at analyzer.js [line 298] this._dependenciesStream.end(); is being called after the final dependency is processed, but later on it is trying to write the shared_bundle_x.js files to the stream after it is ended (at analyzer.js [line 426]) . It is also trying to write the share_bundle files to the ended stream in version 3.9.1 of gulp, but it does not throw an error. Seems like a bug to write the shared_bundle files to the _dependenciesStream even if it wasn't ended.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!