You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[14:31:15] Using gulpfile ~/src/gulp-test/gulpfile.js
[14:31:15] Starting 'default'...
And exits. The return code is 0, and nothing seems to show up with node-inspector. The files actually get copied:
dist
├── bar
│ └── file2
└── foo
└── file1
But the task fails, and gulp quits; if I chain another task in series, it doesn't run. If I remove the destinations and pipe the merged stream to a common destination, the task succeeds.
I think better error management is being addressed elsewhere, so this issue is just about clarifying or addressing the behavior of these merged streams.
Not sure if I've fundamentally misunderstood how these streams behave, but this recipe expresses the behavior I'm trying to achieve.
The text was updated successfully, but these errors were encountered:
EventStream is no longer supported because it is streams1, won't be updated and its merge method isn't a real stream. The open ticket for this is gulpjs/async-done#19
Hi. In the 4.0 branch, I'm having trouble merging two streams that are distinctly piped to destinations. Consider this gulpfile:
Running
gulp
gets me:And exits. The return code is 0, and nothing seems to show up with node-inspector. The files actually get copied:
But the task fails, and gulp quits; if I chain another task in series, it doesn't run. If I remove the destinations and pipe the merged stream to a common destination, the task succeeds.
I think better error management is being addressed elsewhere, so this issue is just about clarifying or addressing the behavior of these merged streams.
Not sure if I've fundamentally misunderstood how these streams behave, but this recipe expresses the behavior I'm trying to achieve.
The text was updated successfully, but these errors were encountered: