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
Hey, thanks for building this. Minor thing, but first time I ran the bridge port 3000 was in use, so I experienced the following console output:
events.js:182
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE :::3000
at Object._errnoException (util.js:1041:11)
at _exceptionWithHostPort (util.js:1064:20)
at Server.setupListenHandle [as _listen2] (net.js:1322:14)
at listenInCluster (net.js:1370:12)
at Server.listen (net.js:1466:7)
at Object.createServer (/usr/local/lib/node_modules/ever-layout-bridge/lib/network.js:26:8)
at Object.<anonymous> (/usr/local/lib/node_modules/ever-layout-bridge/lib/ever-layout-bridge.js:66:9)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)```
Fairly clear from the stack track but a friendly one-line message error (or auto alternate port selection) would be solid.
The text was updated successfully, but these errors were encountered:
@Stitarmare The issue being reported is just that the error message is ugly. I'm embarrassed to admit that I still haven't looked into this... but I will! If you're seeing this error though you can resolve it by hosting on a different port:
Hey, thanks for building this. Minor thing, but first time I ran the bridge port 3000 was in use, so I experienced the following console output:
The text was updated successfully, but these errors were encountered: