-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled 'error' event
error in gulp 5
#2802
Comments
The merge-stream package is no longer supported, as it isn't a properly behaving stream. You can instead use the ordered-read-stream package that the gulpjs team maintains, which has the same interface/usage as merge-stream. |
For posterity, all streams using |
Great, thanks, I'll try ordered-read-streams. Could we please maybe have some better error message for this? AFAIK merge-stream has been considered the de facto standard way to do this, so I think I won't be the last person to get confused by this... Thanks! |
…reams` dependency The `merge-stream` dependency is no longer maintained and doesn't work in combination with Gulp 5 anymore (for more information refer to gulpjs/gulp#2802 (comment)). Fortunately the Gulp team maintains a drop-in replacement dependency called `ordered-read-streams` with the same API as `merge-stream`. Indeed, running all affected Gulp targets and comparing build artifacts with `diff -r <old> <new>` confirms that no unexpected changes are made. Fixes a part of mozilla#17922.
- Set `encoding` to false to ensure same encoding behavior as Gulp 4. - Replace `merge-stream` with `ordered-read-streams` because of gulpjs/gulp#2802 (comment).
Having the same issue here, after upgrading to Gulp 5. I have a number of I was trying to do one by one, and then in one big It seems that no matter what, if there are 3 items in that src array, it's enough to start triggering this crash. Definitely something related to I thought I was going to just have to separate all the streams into a big series of many functions, as I'll give a try to |
Yeah, it worked for me, by just changing:
to:
(and installing |
- Set `encoding` to false to ensure same encoding behavior as Gulp 4. - Replace `merge-stream` with `ordered-read-streams` because of gulpjs/gulp#2802 (comment).
Before you open this issue, please complete the following tasks:
What were you expecting to happen?
I updated my repo from gulp 4 to gulp 5 (scout-handbook/odymaterialy.skauting.cz#12), I expected no errors.
What actually happened?
Please give us a sample of your gulpfile
I created a small repro here: https://gist.github.com/marekdedic/ba636b4fcbf233d65a63b8c1720b057d
Run
npm ci && gulp main
to see the issueTerminal output / screenshots
See above the output.
Please provide the following information:
Additional information
At first I thought this was an issue with
merge-stream
, it's author claims it's not. See grncdr/merge-stream#42.The text was updated successfully, but these errors were encountered: