When flow fails to start, sometimes you get an empty error message

diegodurli / flow-status-webpack-plugin

Run Flow Status on each Webpack build.

MIT License

98 stars 16 forks source link

When flow fails to start, sometimes you get an empty error message #19

Open martynsmith opened 8 years ago

martynsmith commented 8 years ago

My flow was failing to start with this error:

/app/react/node_modules/flow-bin/flow-linux64-v0.33.0/flow: error while loading shared libraries: libelf.so.1: cannot open shared object file: No such file or directory

Unfortunately because it was on STDERR, and the checkItWreckIt function is creating an error object using STDOUT, I was getting a webpack error of ERROR in (i.e. error in empty string).

Perhaps the code could be altered to pass both STDOUT and STDERR ?

diegodurli commented 8 years ago

Hey @martynsmith!

Yes, I guess that's exactly it! Would you be willing to submit a PR to fix it?

Thank you!

DBosley commented 6 years ago

This problem still exists and causes problems with webpack dev server and webpack-serve