question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Event.js unhandeled error event

See original GitHub issue

I keep getting this error when running npm run dev, i’m using the browserify version

> woording-web@0.0.2 dev /Users/cor/Development/woording/woording-web
> watchify -vd -p browserify-hmr -e src/main.js -o dist/build.js & http-server -c 1 -a localhost

events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: listen EADDRINUSE
    at exports._errnoException (util.js:746:11)
    at Server._listen2 (net.js:1156:14)
    at listen (net.js:1182:10)
    at net.js:1280:9
    at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:81:16)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:99:10)

npm ERR! Darwin 15.2.0
npm ERR! argv "node" "/usr/local/bin/npm" "run" "dev"
npm ERR! node v0.12.3
npm ERR! npm  v3.3.12
npm ERR! code ELIFECYCLE
npm ERR! woording-web@0.0.2 dev: `watchify -vd -p browserify-hmr -e src/main.js -o dist/build.js & http-server -c 1 -a localhost`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the woording-web@0.0.2 dev script 'watchify -vd -p browserify-hmr -e src/main.js -o dist/build.js & http-server -c 1 -a localhost'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the woording-web package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     watchify -vd -p browserify-hmr -e src/main.js -o dist/build.js & http-server -c 1 -a localhost
npm ERR! You can get their info via:
npm ERR!     npm owner ls woording-web
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/cor/Development/woording/woording-web/npm-debug.log

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
yyx990803commented, Jan 21, 2016

EADDRINUSE means your 8080 port is already in use.

0reactions
corcommented, Jan 26, 2016

It had something to do with our (@PhiliPdB, @LeonGr and I) school network, sorry for the inconvenience.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Node.js – events js 72 throw er unhandled 'error' event
Close nodejs app running in another shell. Restart the terminal and run the program again. Another server might be also using the same...
Read more >
How to Fix "throw er; // Unhandled 'error' event"?
It's only affecting watch -command and appears to be linked to a file-system incompatibility when watching file changes. The line number ...
Read more >
How to Fix “throw er; // Unhandled 'error' event”?
Try to install above npm package. It has resolved my issue. If it doesn't help then it may be cache problem.
Read more >
events.js:291 throw er; // Unhandled 'error' event #2958
Node.js Version: v14.5.0 OS: Debian 9 Scope (install, code, runtime, meta, other?): code Module (and version) (if relevant): I don't know ...
Read more >
Element: error event - Web APIs | MDN
The error event is fired on an Element object when a resource failed to load, or can't be used. For example, if a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found