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
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
The semantics of a stream's error event are that it went berzerk and can't continue operating. And that is good for the common case. What you might want to do is emit warning events, or any other event without predefined semantics, and then implement your own handling.
If user is able to handle error (or attached
on('error', ...)
handler on stream - then we should not callcleanup
on piped streams.I think this two lines should be in reverse order.
We encountered this problem inside this tasks: gulpjs/gulp#91 and gulpjs/gulp#75
The text was updated successfully, but these errors were encountered: