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
If I start a second instance of a node-livereload server, I get the follow message and a stack trace, which is to be expected:
Error: listen EADDRINUSE :::35729
... stacktrace here ...
However, I can't figure out a way to catch and prevent this message from being printed in the console. I've tried try/catch, but the error happens asynchronously (and probably in another process?).
My use-case for this: I'd like to be able to catch the error and print a friendlier error message, like "Unable to start the LiveReload server! This is most likely because you have another instance of the LiveReload server running on this port."
The text was updated successfully, but these errors were encountered:
If I start a second instance of a
node-livereload
server, I get the follow message and a stack trace, which is to be expected:However, I can't figure out a way to catch and prevent this message from being printed in the console. I've tried
try/catch
, but the error happens asynchronously (and probably in another process?).My use-case for this: I'd like to be able to catch the error and print a friendlier error message, like "Unable to start the LiveReload server! This is most likely because you have another instance of the LiveReload server running on this port."
The text was updated successfully, but these errors were encountered: