Skip to content
This repository was archived by the owner on May 16, 2025. It is now read-only.

fix: Error: write EPIPE (Issue #118) #121

Merged

Conversation

DreierF
Copy link
Contributor

@DreierF DreierF commented Feb 8, 2020

This PR fixes #118. The underlying problem seem to be a bug in node.js >=10 (nodejs/node#26828), but not entirely sure as I got the same behavior on MacOS with Node 13.7.0. Using a stream instead resolved the issue for me.

@DreierF DreierF force-pushed the issue/118_fix_epipe_error branch from 549bb8c to 81ac539 Compare February 9, 2020 13:51
@ChadKillingsworth
Copy link
Member

Readable.from is definitely preferable, but it doesn't look like it was added until Node 12. So we'll need 2 different paths for now.

@ChadKillingsworth
Copy link
Member

Since you can recreate this, would you be able to test a solution like https://stackoverflow.com/a/44091532/1211524 ?

@DreierF
Copy link
Contributor Author

DreierF commented Feb 14, 2020

This solution also fixes the issue.

@ChadKillingsworth
Copy link
Member

Awesome - thanks

@ChadKillingsworth ChadKillingsworth merged commit b4e18e3 into webpack-contrib:master Feb 22, 2020
@schmidtk schmidtk mentioned this pull request Sep 8, 2020
@schmidtk
Copy link
Contributor

schmidtk commented Sep 8, 2020

@ChadKillingsworth I was able to recreate this by passing invalid options to the compiler. In my specific case, I was using the useOfGoogBase error group and updated the compiler to 20200830.0.0 which has removed that group. I have a fix for this in #146.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error: write EPIPE
3 participants