jackblog-react-redux write EPIPE

[yuanzougaofei97]

• Version:
  v4.4.2
• Platform:
  3.10.0-229.el7.x86_64
• Subsystem:
  webpack

console output:

> jackblog-react-redux@2.1.0 dev /var/lib/nodejs/jackblog-react-redux-master
> npm-run-all --sequential build-server:dev start-dev


> jackblog-react-redux@2.1.0 build-server:dev /var/lib/nodejs/jackblog-react-redux-master
> better-npm-run build-dev-server

running better-npm-run in /var/lib/nodejs/jackblog-react-redux-master
Executing script: build-dev-server

to be executed: webpack --colors --config ./webpack/webpack.config.dev.server.js 
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at exports._errnoException (util.js:870:11)
    at WriteWrap.afterWrite (net.js:769:14)

npm ERR! Linux 3.10.0-229.el7.x86_64
npm ERR! argv "/var/lib/nodejs/node-v4.4.2-linux-x64/bin/node" "/var/lib/nodejs/node-v4.4.2-linux-x64/bin/npm" "run-script" "build-server:dev"
npm ERR! node v4.4.2
npm ERR! npm  v2.15.0
npm ERR! code ELIFECYCLE
npm ERR! jackblog-react-redux@2.1.0 build-server:dev: `better-npm-run build-dev-server`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the jackblog-react-redux@2.1.0 build-server:dev script 'better-npm-run build-dev-server'.
npm ERR! This is most likely a problem with the jackblog-react-redux package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     better-npm-run build-dev-server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs jackblog-react-redux
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! 
npm ERR!     npm owner ls jackblog-react-redux
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /var/lib/nodejs/jackblog-react-redux-master/npm-debug.log
ERROR: build-server:dev: None-Zero Exit(1);

npm ERR! Linux 3.10.0-229.el7.x86_64
npm ERR! argv "/var/lib/nodejs/node-v4.4.2-linux-x64/bin/node" "/var/lib/nodejs/node-v4.4.2-linux-x64/bin/npm" "run" "dev"
npm ERR! node v4.4.2
npm ERR! npm  v2.15.0
npm ERR! code ELIFECYCLE
npm ERR! jackblog-react-redux@2.1.0 dev: `npm-run-all --sequential build-server:dev start-dev`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the jackblog-react-redux@2.1.0 dev script 'npm-run-all --sequential build-server:dev start-dev'.
npm ERR! This is most likely a problem with the jackblog-react-redux package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm-run-all --sequential build-server:dev start-dev
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs jackblog-react-redux
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! 
npm ERR!     npm owner ls jackblog-react-redux
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /var/lib/nodejs/jackblog-react-redux-master/npm-debug.log

log output:

0 info it worked if it ends with ok
1 verbose cli [ '/var/lib/nodejs/node-v4.4.2-linux-x64/bin/node',
1 verbose cli   '/var/lib/nodejs/node-v4.4.2-linux-x64/bin/npm',
1 verbose cli   'run',
1 verbose cli   'dev' ]
2 info using npm@2.15.0
3 info using node@v4.4.2
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info predev jackblog-react-redux@2.1.0
6 info dev jackblog-react-redux@2.1.0
7 verbose unsafe-perm in lifecycle true
8 info jackblog-react-redux@2.1.0 Failed to exec dev script
9 verbose stack Error: jackblog-react-redux@2.1.0 dev: `npm-run-all --sequential build-server:dev start-dev`
9 verbose stack Exit status 1
9 verbose stack     at EventEmitter.<anonymous> (/var/lib/nodejs/node-v4.4.2-linux-x64/lib/node_modules/npm/lib/utils/lifecycle.js:217:16)
9 verbose stack     at emitTwo (events.js:87:13)
9 verbose stack     at EventEmitter.emit (events.js:172:7)
9 verbose stack     at ChildProcess.<anonymous> (/var/lib/nodejs/node-v4.4.2-linux-x64/lib/node_modules/npm/lib/utils/spawn.js:24:14)
9 verbose stack     at emitTwo (events.js:87:13)
9 verbose stack     at ChildProcess.emit (events.js:172:7)
9 verbose stack     at maybeClose (internal/child_process.js:827:16)
9 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
10 verbose pkgid jackblog-react-redux@2.1.0
11 verbose cwd /var/lib/nodejs/jackblog-react-redux-master
12 error Linux 3.10.0-229.el7.x86_64
13 error argv "/var/lib/nodejs/node-v4.4.2-linux-x64/bin/node" "/var/lib/nodejs/node-v4.4.2-linux-x64/bin/npm" "run" "dev"
14 error node v4.4.2
15 error npm  v2.15.0
16 error code ELIFECYCLE
17 error jackblog-react-redux@2.1.0 dev: `npm-run-all --sequential build-server:dev start-dev`
17 error Exit status 1
18 error Failed at the jackblog-react-redux@2.1.0 dev script 'npm-run-all --sequential build-server:dev start-dev'.
18 error This is most likely a problem with the jackblog-react-redux package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error     npm-run-all --sequential build-server:dev start-dev
18 error You can get information on how to open an issue for this project with:
18 error     npm bugs jackblog-react-redux
18 error Or if that isn't available, you can get their info via:
18 error
18 error     npm owner ls jackblog-react-redux
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]

[mscdex]

Perhaps this would be better filed at the webpack issue tracker?

[Fishrock123]

npm ERR! This is most likely a problem with the jackblog-react-redux package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm-run-all --sequential build-server:dev start-dev
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs jackblog-react-redux
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! 
npm ERR!     npm owner ls jackblog-react-redux
npm ERR! There is likely additional logging output above.

... that being said I'm 99% sure this is a duplicate of #947

"EPIPE errors thrown when piping to a closed stream"

[Fishrock123]

I don't think we can help you more without knowing what your npm scripts look like, but in any case it is probably the above issue.

You can "fix" this by ensuring you always consume all of the stdio output in a unix pipe (|).