Warning: file_get_contents(/data/phpspider/zhask/data//catemap/6/mongodb/13.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Javascript NPM跑步观察错误!错误[ERR\u STREAM\u destromed]:在流被销毁后无法调用write_Javascript_Node.js_Npm_Node Modules - Fatal编程技术网

Javascript NPM跑步观察错误!错误[ERR\u STREAM\u destromed]:在流被销毁后无法调用write

Javascript NPM跑步观察错误!错误[ERR\u STREAM\u destromed]:在流被销毁后无法调用write,javascript,node.js,npm,node-modules,Javascript,Node.js,Npm,Node Modules,我忘记了我以前做过的事。当我运行代码时,会出现一些错误。我寻找解决问题的方法,并总是这样尝试 我清除了缓存,但仍然出错。我删除了node_模块并再次安装,但仍然出错。我试着在一些网站上发一篇帖子,但还是出错了 i use : node v 10.15.3 npm v 6.4.1 error's code : Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed at doWrite (_

我忘记了我以前做过的事。当我运行代码时,会出现一些错误。我寻找解决问题的方法,并总是这样尝试

我清除了缓存,但仍然出错。我删除了node_模块并再次安装,但仍然出错。我试着在一些网站上发一篇帖子,但还是出错了

i use :
node v 10.15.3
npm v 6.4.1

error's code :
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
    at doWrite (_stream_writable.js:406:19)
    at writeOrBuffer (_stream_writable.js:394:5)
    at WriteStream.Writable.write (_stream_writable.js:294:11)
    at goToLineStart (D:\PHP\order\node_modules\webpack\lib\ProgressPlugin.js:90:27)
    at defaultHandler (D:\PHP\order\node_modules\webpack\lib\ProgressPlugin.js:74:4)
    at update (D:\PHP\order\node_modules\webpack\lib\ProgressPlugin.js:169:5)
    at moduleAdd (D:\PHP\order\node_modules\webpack\lib\ProgressPlugin.js:181:5)
    at SyncHook.eval [as call] (eval at create (D:\PHP\order\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonym
ous>:7:1)
    at Compilation.buildModule (D:\PHP\order\node_modules\webpack\lib\Compilation.js:712:26)
    at factory.create (D:\PHP\order\node_modules\webpack\lib\Compilation.js:960:14)
    at factory (D:\PHP\order\node_modules\webpack\lib\NormalModuleFactory.js:409:6)
    at hooks.afterResolve.callAsync (D:\PHP\order\node_modules\webpack\lib\NormalModuleFactory.js:155:13)
    at AsyncSeriesWaterfallHook.eval [as callAsync] (eval at create (D:\PHP\order\node_modules\tapable\lib\HookCodeFacto
ry.js:33:10), <anonymous>:6:1)
    at AsyncSeriesWaterfallHook.lazyCompileHook (D:\PHP\order\node_modules\tapable\lib\Hook.js:154:20)
    at resolver (D:\PHP\order\node_modules\webpack\lib\NormalModuleFactory.js:138:29)
    at process.nextTick (D:\PHP\order\node_modules\webpack\lib\NormalModuleFactory.js:346:9)
    at process._tickCallback (internal/process/next_tick.js:61:11)
Emitted 'error' event at:
    at onwriteError (_stream_writable.js:425:12)
    at onwrite (_stream_writable.js:456:5)
    at doWrite (_stream_writable.js:406:11)
    at writeOrBuffer (_stream_writable.js:394:5)
    [... lines matching original stack trace ...]
    at process._tickCallback (internal/process/next_tick.js:61:11)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! order@1.0.0 development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-
modules --config=node_modules/laravel-mix/setup/webpack.config.js "--watch"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the order@1.0.0 development script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\USER\AppData\Roaming\npm-cache\_logs\2019-07-24T08_11_44_990Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! order@1.0.0 watch: `npm run development -- --watch`
npm ERR! Exit status 1
npm ERR!`enter code here`
npm ERR! Failed at the order@1.0.0 watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\USER\AppData\Roaming\npm-cache\_logs\2019-07-24T08_11_45_008Z-debug.log
我使用:
节点v 10.15.3
npm v 6.4.1
错误代码:
错误[ERR\u STREAM\u destromed]:在流被销毁后无法调用write
在doWrite(_stream_writable.js:406:19)
在writeOrBuffer(_stream_writeable.js:394:5)
在WriteStream.Writable.write(_stream_Writable.js:294:11)
在Gotolistart(D:\PHP\order\node\u modules\webpack\lib\ProgressPlugin.js:90:27)
位于defaultHandler(D:\PHP\order\node\u modules\webpack\lib\ProgressPlugin.js:74:4)
更新时(D:\PHP\order\node\u modules\webpack\lib\ProgressPlugin.js:169:5)
位于moduleAdd(D:\PHP\order\node\u modules\webpack\lib\ProgressPlugin.js:181:5)
在SyncHook.eval[作为调用](在创建时进行评估(D:\PHP\order\node\u modules\tapable\lib\HookCodeFactory.js:19:10),:7:1)
在Compilation.buildModule(D:\PHP\order\node\u modules\webpack\lib\Compilation.js:712:26)
在factory.create(D:\PHP\order\node\u modules\webpack\lib\Compilation.js:960:14)
在工厂(D:\PHP\order\node\u modules\webpack\lib\NormalModuleFactory.js:409:6)
在hooks.afterResolve.callAsync(D:\PHP\order\node\u modules\webpack\lib\NormalModuleFactory.js:155:13)
在AsyncSeriesWaterWallHook.eval[作为callAsync](在创建时进行eval)(D:\PHP\order\node\u modules\tapable\lib\hookCodeFactor
ry.js:33:10),:6:1)
在AsyncSeriesWaterWallHook.lazyCompileHook(D:\PHP\order\node\u modules\tapable\lib\Hook.js:154:20)
在解析器(D:\PHP\order\node\u modules\webpack\lib\NormalModuleFactory.js:138:29)
位于process.nextTick(D:\PHP\order\node\u modules\webpack\lib\NormalModuleFactory.js:346:9)
在进程中。_tick回调(内部/process/next_tick.js:61:11)
在以下位置发出“错误”事件:
在onwriteError(_stream_writable.js:425:12)
在onwrite(_stream_writable.js:456:5)
在doWrite(_stream_writable.js:406:11)
在writeOrBuffer(_stream_writeable.js:394:5)
[…与原始堆栈跟踪匹配的行…]
在进程中。_tick回调(内部/process/next_tick.js:61:11)
npm错误!代码失效循环
npm错误!错误1
npm错误!order@1.0.0开发:`cross env NODE\u env=development NODE\u modules/webpack/bin/webpack.js--progress--hide-
模块--config=node_modules/laravel mix/setup/webpack.config.js--watch“`
npm错误!退出状态1
npm错误!
npm错误!失败order@1.0.0开发脚本。
npm错误!这可能不是npm的问题。上面可能还有其他日志输出。
npm错误!此运行的完整日志可在以下位置找到:
npm错误!C:\Users\USER\AppData\Roaming\npm cache\\u logs\2019-07-24T08\u 11\u 44\u 990Z-debug.log
npm错误!代码失效循环
npm错误!错误1
npm错误!order@1.0.0watch:`npm运行开发--watch`
npm错误!退出状态1
npm错误`在这里输入代码`
npm错误!失败order@1.0.0看剧本。
npm错误!这可能不是npm的问题。上面可能还有其他日志输出。
npm错误!此运行的完整日志可在以下位置找到:
npm错误!C:\Users\USER\AppData\Roaming\npm cache\\u logs\2019-07-24T08\u 11\u 45\u 008Z-debug.log
如果要查看日志文件:

[2019-07-24T08_11_45_008Z-debug.log] 0信息如果以“确定”结尾,则有效

1详细cli['C:\Program Files\nodejs\node.exe'

1详细cli'C:\Program Files\nodejs\node\u modules\npm\bin\npm cli.js'

1详细cli“运行”

1详细cli“监视”]

2信息使用npm@6.4.1

3信息使用node@v10.15.3

4详细的运行脚本['prewatch','watch','postwatch']

5信息生命周期order@1.0.0~prewatch:order@1.0.0

6信息生命周期order@1.0.0~z~注意:order@1.0.0

7详细的生命周期order@1.0.0~watch:生命周期中的不安全烫发是真的

8详细的生命周期order@1.0.0~watch:PATH:C:\程序 文件\nodejs\node\u模块\npm\node\u模块\npm生命周期\node gyp- 箱子D:\PHP\order\node\u modules.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\ProgramFiles\Git\cmd;C:\xampp\php;C:\ProgramData\Composer安装程序\bin;C:\ProgramFiles\nodejs\;C:\Users\USER\AppData\Roaming\Composer\vendor\bin;C:\Users\USER\AppData\Roaming\npm

9详细的生命周期order@1.0.0~watch:CWD:D:\PHP\order

10愚蠢的生命周期order@1.0.0~watch:Args:['/d/s/c',npm运行开发--watch']

11愚蠢的生命周期order@1.0.0~watch:Returned:code:1信号:null

12信息生命周期order@1.0.0~watch:无法执行监视脚本

13详细堆栈错误:order@1.0.0监视:
npm运行开发--watch

13详细堆栈退出状态1

13 EventEmitter上的详细堆栈。(C:\方案 Files\nodejs\node\u modules\npm\node\u modules\npm lifecycle\index.js:301:16)

13 EventEmitter.emit上的详细堆栈(events.js:189:13)

13子进程上的详细堆栈。(C:\Program Files\nodejs\node\U modules\npm\node\U modules\npm lifecycle\lib\spawn.js:55:14)

13 ChildProcess.emit上的详细堆栈(events.js:189:13)

13 maybeClose的详细堆栈(internal/child_process.js:970:16)

13 Process.ChildProcess.\u handle.onexit处的详细堆栈(internal/child\u Process.js:259:5)

14详细的pkgidorder@1.0.0

15详细cwd:\PHP\order

16详细窗口\u NT 6.1.7601

17详细argv“C:\Program Files\nodejs\node.exe”“C:\Program Files\nodejs\node\U模块\npm\bin\npm cli.js”“运行”“监视”

18详细节点v10.15.3

19详细的npm v6.4.1

20错误代码ELIFECYCLE

21错误1

22错误order@1.0.0监视:
npm运行开发--watch

22错误退出状态1

23发生错误时失败order@1.0.0看剧本

23错误这可能不是问题