webpack --progress错误：写入EINVAL

我在Windows 10上最近将我的node.js升级到版本7.1.0。每次我用--progress标志运行webpack命令时，我开始出现以下错误。webpack --progress错误：写入EINVAL

$ webpack --progress 
Node Environment: development                                  events.js:160 
     throw er; // Unhandled 'error' event 
    ^

Error: write EINVAL 
    at exports._errnoException (util.js:1022:11) 
    at WriteStream.Socket._writeGeneric (net.js:715:26) 
    at WriteStream.Socket._write (net.js:734:8) 
    at doWrite (_stream_writable.js:334:12) 
    at writeOrBuffer (_stream_writable.js:320:5) 
    at WriteStream.Writable.write (_stream_writable.js:247:11) 
    at WriteStream.Socket.write (net.js:661:40) 
    at E:\Projects\wad\node_modules\webpack\bin\convert-argv.js:421:20 
    at Compiler.<anonymous> (E:\Projects\wad\node_modules\webpack\lib\ProgressPlugin.js:77:4) 
    at Compiler.applyPlugins (E:\Projects\wad\node_modules\tapable\lib\Tapable.js:26:37) 
    at Compiler.<anonymous> (E:\Projects\wad\node_modules\webpack\lib\Compiler.js:193:12) 
    at Compiler.emitRecords (E:\Projects\wad\node_modules\webpack\lib\Compiler.js:282:37) 
    at Compiler.<anonymous> (E:\Projects\wad\node_modules\webpack\lib\Compiler.js:187:11) 
    at E:\Projects\wad\node_modules\webpack\lib\Compiler.js:275:11 
    at Compiler.applyPluginsAsync (E:\Projects\wad\node_modules\tapable\lib\Tapable.js:60:69) 
    at Compiler.afterEmit (E:\Projects\wad\node_modules\webpack\lib\Compiler.js:272:8) 
    at Compiler.<anonymous> (E:\Projects\wad\node_modules\webpack\lib\Compiler.js:267:14) 
    at E:\Projects\wad\node_modules\async\lib\async.js:52:16 
    at done (E:\Projects\wad\node_modules\async\lib\async.js:246:17) 
    at E:\Projects\wad\node_modules\async\lib\async.js:44:16 
    at E:\Projects\wad\node_modules\graceful-fs\graceful-fs.js:43:10 
    at FSReqWrap.oncomplete (fs.js:111:15)

它工作正常，没有--progress标志和webpack --progress正在研究的node.js v6.x.x.罚款在同一个项目中使用webpack --progress与节点v.7.1.0，但另一台Windows 10机器也可以正常工作。

这个错误是什么意思？

来源

2016-11-11 Lennart Twen

看起来像[this]（https://github.com/nodejs/node/issues/9542）bug – asvyazin