You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll have it running for a while, I'll close it out. Run npm start and I'll get the following error:
contract-summary@0.1.0 start /Users/JayStarr/web/contract-summary
> webpack-dashboard -m -- webpack-dev-server --config config/webpack.config.js --open --env.local --hot
internal/process.js:172
throw errnoException(err, 'kill');
^
Error: kill ESRCH
at exports._errnoException (util.js:1026:11)
at process.kill (internal/process.js:172:13)
at process.on (/Users/JayStarr/web/contract-summary/node_modules/webpack-dashboard/bin/webpack-dashboard.js:89:15)
at emitOne (events.js:101:20)
at process.emit (events.js:188:7)
at process.exit (internal/process.js:146:15)
at Screen.Dashboard.screen.key (/Users/JayStarr/web/contract-summary/node_modules/webpack-dashboard/dashboard/index.js:84:15)
at Screen.EventEmitter._emit (/Users/JayStarr/web/contract-summary/node_modules/blessed/lib/events.js:94:20)
at Screen.EventEmitter.emit (/Users/JayStarr/web/contract-summary/node_modules/blessed/lib/events.js:114:17)
at Program.<anonymous> (/Users/JayStarr/web/contract-summary/node_modules/blessed/lib/widgets/screen.js:593:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! contract-summary@0.1.0 start: 'webpack-dashboard -m -- webpack-dev-server --config config/webpack.config.js --open --env.local --hot'
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the contract-summary@0.1.0 start 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! /Users/JayStarr/.npm/_logs/2018-07-13T15_22_42_717Z-debug.log
I'll go and kill all node processes but that won't work. I'm trying to run on port 8080 so I ran the following command to see if anything else is trying to listen on that port:
@CallawayJay I am attempting to recreate the issue on my computer and I want to make sure I am following the exact steps you took.
How long did you have it running for?
How did you closed out the running of your app, server, and/or VSC terminal?
What command was use to kill all your node processes?
This information will help in figuring out what actually happen and if anything warn others of this potential bug. If this is nor longer an issue would love to hear how it was resolved and we will close this issue. Thanks in advance.
I have similar problem when running simple: npx webpack-dashboard -- webpack
When I close dashboard with q or esc can see following error:
internal/process.js:172
throw errors.errnoException(err, 'kill');
^
Error: kill ESRCH
at process.kill (internal/process.js:172:20)
at process.on (/node_modules/webpack-dashboard/bin/webpack-dashboard.js:89:15)
at emitOne (events.js:121:20)
at process.emit (events.js:211:7)
at process.exit (internal/process.js:146:15)
at Screen.Dashboard.screen.key (/node_modules/webpack-dashboard/dashboard/index.js:84:15)
at Screen.EventEmitter._emit (/node_modules/blessed/lib/events.js:94:20)
at Screen.EventEmitter.emit (/node_modules/blessed/lib/events.js:114:17)
at Program.<anonymous> (/node_modules/blessed/lib/widgets/screen.js:593:12)
at emitTwo (events.js:126:13)
Command is executed on linux server inside tmux pane.
Uh oh!
There was an error while loading. Please reload this page.
I'll have it running for a while, I'll close it out. Run npm start and I'll get the following error:
I'll go and kill all node processes but that won't work. I'm trying to run on port 8080 so I ran the following command to see if anything else is trying to listen on that port:
sudo lsof -i -n -P | grep TCP
And this is the output:
Nothing is listening on 8080... The only way i can get it working again is restarting my computer. Then it works fine.
====================================================================
More Details
I'm on a mac
I'm using the terminal in vs code
webpack-dashboard version 2.0.0
The output of running
echo $TERM
= xterm-256colorThe text was updated successfully, but these errors were encountered: