Annoying warnings

[Timer]

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
joes-mbp:test-next joe$ { Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write'}
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }
{ Error: EPIPE: broken pipe, write errno: -32, code: 'EPIPE', syscall: 'write' }

Where did these come from?

[gaearon]

Which command?

[Timer]

yarn build, I suspect this is workers from thread-loader dying off

[Timer]

Warm cache:
Thread loader disabled: Done in 33.35s.
Thread loader enabled: ✨ Done in 31.10s.

Cold:
Thread loader disabled: Done in 71.03s.
Thread loader enabled: ✨ Done in 59.11s

We can probably turn this off TBH, webpack 4 is pretty fast. The gains were way more impressive with webpack 3. I think we could find some low-hanging fruit to optimize in webpack/our toolchain.

thread-loader prob isn't maintained enough to be worth this burden overhead and super complicated webpack message parsing.

[gaearon]

I’m cool with this. And I think ideally we’d want to build on top of jest-worker instead because we know it’s solid and well-maintained. Actually might be worth a try taking thread-loader and rewriting to work on top of that.