latest update of libuv breaks a lot of things, that is why i think that the problem is in node itself.
returning to old libuv version fixes all of the problems.
npm, yarn throws error Error: read ENOTCONN
yarn example error stack:
yarn install --ignore-engines
yarn install v1.3.2
info No lockfile found.
[1/4] Resolving packages...
⢀ [email protected]:137
throw er; // Unhandled 'error' event
^
Error: read ENOTCONN
at _errnoException (util.js:1003:13)
at Socket._read (net.js:495:20)
at Socket.Readable.read (_stream_readable.js:449:10)
at Socket.read (net.js:376:43)
at new Socket (net.js:259:12)
at createSocket (internal/child_process.js:241:11)
at ChildProcess.spawn (internal/child_process.js:357:23)
at Object.exports.spawn (child_process.js:499:9)
at default (****/npm/lib/node_modules/yarn/lib/cli.js:29936:24)
at new Promise (<anonymous>)
webpack error Error: write EPIPE
full error stack:
events.js:137
throw er; // Unhandled 'error' event
^
Error: write EPIPE
at _errnoException (util.js:1003:13)
at Socket._writeGeneric (net.js:763:25)
at Socket._write (net.js:782:8)
at doWrite (_stream_writable.js:407:12)
at writeOrBuffer (_stream_writable.js:393:5)
at Socket.Writable.write (_stream_writable.js:290:11)
at PoolWorker.writeJson (****/node_modules/thread-loader/dist/WorkerPool.js:85:22)
at PoolWorker.run (****/node_modules/thread-loader/dist/WorkerPool.js:65:12)
at WorkerPool.distributeJob (****/node_modules/thread-loader/dist/WorkerPool.js:333:17)
at ****/node_modules/thread-loader/node_modules/async/queue.js:10:5
at Object.process (****/node_modules/thread-loader/node_modules/async/internal/queue.js:175:17)
at ****/node_modules/thread-loader/node_modules/async/internal/queue.js:82:19
at Immediate.<anonymous> (****/node_modules/thread-loader/node_modules/async/internal/setImmediate.js:27:16)
at runCallback (timers.js:756:18)
at tryOnImmediate (timers.js:717:5)
at processImmediate [as _immediateCallback] (timers.js:697:5)
Waiting for the debugger to disconnect...
Error: write EPIPE
util.js:1003
at _errnoException (util.js:1003:13)
at Socket._writeGeneric (net.js:763:25)
at Socket._write (net.js:782:8)
at doWrite (_stream_writable.js:407:12)
at writeOrBuffer (_stream_writable.js:393:5)
at Socket.Writable.write (_stream_writable.js:290:11)
at PoolWorker.writeJson (****/node_modules/thread-loader/dist/WorkerPool.js:85:22)
at PoolWorker.run (****/node_modules/thread-loader/dist/WorkerPool.js:65:12)
at WorkerPool.distributeJob (****/node_modules/thread-loader/dist/WorkerPool.js:333:17)
at ****/node_modules/thread-loader/node_modules/async/queue.js:10:5
at Object.process (****/node_modules/thread-loader/node_modules/async/internal/queue.js:175:17)
at ****/node_modules/thread-loader/node_modules/async/internal/queue.js:82:19
at Immediate.<anonymous> (****/node_modules/thread-loader/node_modules/async/internal/setImmediate.js:27:16)
at runCallback (timers.js:756:18)
at tryOnImmediate (timers.js:717:5)
at processImmediate [as _immediateCallback] (timers.js:697:5)
latest update of libuv breaks a lot of things, that is why i think that the problem is in node itself.
returning to old libuv version fixes all of the problems.
npm, yarn throws error
Error: read ENOTCONNyarn example error stack:
webpack error
Error: write EPIPEfull error stack: