-
-
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
Error: premature close #2086
Comments
@mimoduo Thanks! I believe I see 2 problems:
|
P.S. Did you know that we published the official 4.0.0 on npm? Install it with |
Sweet! Thanks for the thorough response @phated!
P.S. Keep rocking gulp and being awesome! |
@mimoduo cheers! I just hacked up gulp-modernizr to insert my 2 changes into your boilerplate and it works after the changes. Hopefully you're able to get the author to respond. |
Btw, it looks like a lot of your tree has outdated vinyl code in it (v2.1.0 is latest) - I'd recommend moving away from those or getting them to upgrade:
|
Hi ! Same problem here. I installed gulp with next and always the same issue.
|
Hei Same Error. I tried also with gulp@next, still the same Error.
I'm using |
@firestar300 @dario-baumberger as stated above, this is due to your dependencies using outdated dependencies. If you prepare a reproduction repo for me to poke at, I could tell you which dependencies are busted, but you haven't seem to have done that. |
To anyone thinking about posting here: supply a reproduction repo so I can actually see which dependency is busted or I can't help you. |
This error is also raised if you try to output to a directory that exists, but isn’t writable (for instance, if it’s a symlink to a directory that no longer exists).
Much less likely than outdated dependencies, but some users may arrive here because of that.
… On 9 Jan 2018, at 15:13, Blaine Bublitz ***@***.***> wrote:
To anyone thinking about posting here: supply a reproduction repo so I can actually see which dependency is busted or I can't help you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#2086 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGqzZx3ftJxj709eW6doViIFjvWLLrXks5tI54dgaJpZM4RTXJ_>.
|
@cristianl if that's true, give me a reproduction repo so I can fix the bug in vinyl-fs 😒 |
Hi @phated, here's a reproduction repo. https://github.com/ssdatar/gulp-test-repo I am getting a similar error on Mac OS High Sierra 10.13.2. Here is my other system information.
|
@ssdatar thanks! Have you run |
@phated Not sure it's worth investigating as it may be intended behavior/too much of an edge case, but here's the example: https://github.com/cristianl/testcase-vinyl-bug Off-topic: thank you for shipping v4 and the sometimes thankless task of maintaining Gulp and the ecosystem! I'll take some time to hunt for outdated dependencies and open PRs. |
Thanks, @phated! That fixed it for me. Appreciate your help. |
@cristianl thanks for making a reproduction case for me. I was able to boil it down to the simplest case in our dependencies. I'm hoping to hear back on it soon. |
@phated Thanks for your reply. Here's a reproduction repo: https://github.com/dario-baumberger/test-gulp |
@dario-baumberger your modules are extremely out-of-date and seem to be abandoned. They are using the deprecated gulp-util module which won't work with gulp 4. I suggest you find new plugins to use. |
The branch here seems to hit this error if you run |
Hey all, I just published a fix to cc @gauntface |
@cristianl Thanks for the reproduction case, it really helped me dig into this problem and get it solved! |
I removed my dependency on |
@rogperez with gulp 4, there's no need to use |
Ah great! @phated |
I still get this error with the minimal example shown in this gist and all fully updated versions of everything (as far as I can tell). That includes just these:
Error:
|
@phated Would you prefer I open a new issue rather than comment on this closed one? It seems like the same issue to me, but I can start a new one if you prefer. |
You can't use pump without a callback. I think you might want to switch to the readable-stream module and use the pipeline method. The nodejs team took my patch but pump wouldn't. |
I googled around a bit, but my apologies for not being able to figure out what you meant by this. Do you by any chance have a link to the techniques you're describing here? Sorry for my lack of gulp expertise. |
@nathancarter Sorry, it's in Node's core docs at https://nodejs.org/api/stream.html#stream_stream_pipeline_streams_callback - it's easier to recommend |
Got it. Just a plain old chain of |
Glad you solved it. We'll hopefully be writing up a document at some point explaining why plain pipe is bad 😛 |
Hey guys! First of all, I wanna say that gulp has been a game changer since I picked it up at the beginning. You guys make task running super duper easy and quick ~ Thank you for all your hard work!
Now for the juicy bits: My team has been running into an error related to the new alpha and I just hope there's a simple duh moment in there. I made sure to check stack overflow and other repos if the issue was encountered before. I even tried to rollback to a previous alpha build with a bit of luck in between. Here's the detailed error log and the gulpfile:
CLI version 2.0.0
Local version 4.0.0-alpha.3
https://github.com/Fastspot/Boilerplate/blob/dev/gulpfile.js#L389
Any help is appreciated and as always keep up the amazing work!
The text was updated successfully, but these errors were encountered: