Error: premature close
See original GitHub issueHey 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
[12:49:38] Starting 'modernizr'...
>> Explicitly excluding these tests:
>> hidden
Looking for Modernizr references
>> 4 matches in /Users/bryanstoner/Documents/Development/nei/css/site.css
>> csstransforms, csstransforms3d, search, touchevents
>> Ready to build using these settings:
>> load, setClasses, testProp, fnBind
Building your customized Modernizr...OK
Error: Received a non-Vinyl object in `dest()`
at DestroyableTransform.normalize [as _transform] (/Users/bryanstoner/Documents/Development/nei/node_modules/vinyl-fs/lib/dest/prepare.js:16:17)
at DestroyableTransform.Transform._read (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_transform.js:182:10)
at DestroyableTransform.Transform._write (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_transform.js:170:83)
at doWrite (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_writable.js:406:64)
at writeOrBuffer (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_writable.js:395:5)
at DestroyableTransform.Writable.write (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_writable.js:322:11)
at Pumpify.Duplexify._write (/Users/bryanstoner/Documents/Development/nei/node_modules/duplexify/index.js:201:22)
at doWrite (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_writable.js:406:64)
at writeOrBuffer (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_writable.js:395:5)
at Pumpify.Writable.write (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_writable.js:322:11)
at Duplexify.ondata (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_readable.js:612:20)
at Duplexify.emit (events.js:159:13)
at addChunk (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_readable.js:284:12)
at readableAddChunk (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_readable.js:271:11)
at Duplexify.Readable.push (/Users/bryanstoner/Documents/Development/nei/node_modules/readable-stream/lib/_stream_readable.js:238:10)
at Duplexify._forward (/Users/bryanstoner/Documents/Development/nei/node_modules/duplexify/index.js:163:26)
[12:49:39] 'modernizr' errored after 1.08 s
[12:49:39] Error: premature close
at Pumpify.onclose (/Users/bryanstoner/Documents/Development/nei/node_modules/end-of-stream/index.js:43:67)
at Pumpify.emit (events.js:159:13)
at Pumpify.Duplexify._destroy (/Users/bryanstoner/Documents/Development/nei/node_modules/duplexify/index.js:192:8)
at /Users/bryanstoner/Documents/Development/nei/node_modules/duplexify/index.js:175:10
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickDomainCallback (internal/process/next_tick.js:218:9)
[12:49:39] 'build' errored after 3.06 s
[12:49:39] 'default' errored after 3.07 s
[12:49:39] The following tasks did not complete: <series>, sprite
[12:49:39] Did you forget to signal async completion?
Any help is appreciated and as always keep up the amazing work!
Issue Analytics
- State:
- Created 6 years ago
- Comments:31 (17 by maintainers)
Top Results From Across the Web
npm ERR! premature close when using npm install
In my case, the package I was trying to install had a dependency on a Git repository that didn't have a package.json defined...
Read more >"premature close" error during npm install from git url #1 - GitHub
I know/see, that this repo doesn't have package.json, and I do npm install https://github.com/coryetzkorn/state-svg-defs.git Also tried ssh.
Read more >[Gatling 3.0.-RC2] Premature close - Google Groups
If the duration passed into holdFor() is not long enough for all requests to be processed with a response, a number "premature close"...
Read more >Avoiding premature closure in sequential diagnosis - PubMed
On the other hand, the reasoner must be careful to avoid the error, known as premature closure, of accepting a diagnosis before it...
Read more >I cant create react app - Reddit
... Premature close at new NodeError (node:internal/errors:371:5) at PassThrough.onclose (node:internal/streams/end-of-stream:122:30) at ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey all, I just published a fix to
async-done
(v1.2.4) that will allow you to see the errors from your tasks, instead of “premature close”. Please make sure to update your dependencies (it might not happen automatically because of the terribleness of npm’s package-lock files).cc @gauntface
@rogperez with gulp 4, there’s no need to use
gulp-add-src
- I spent a lot of time figuring out how to makegulp.src
a Readable and Transform stream.