Closed Nicholaiii closed 4 months ago
Hey, I noticed such a behaviour as well in the past and it is indeed confusing. This is definitely to be dealt with in the /platform package. Based on the nodejs docs, this error is reported when a close
is called upon a not running server. I'll try to investigate in the effect/platform codebase.
Hey, Tim released a fix. I just tried it locally and I'm getting beautiful and meaningful listen EADDRINUSE: address already in use :::3000
error message 🎉
As is, the library does not handle the case of a port already being in use, instead it just errors (presumably after a timeout) when it realises it's not listening:
This provides almost no context for the actual error, and it's very hard to debug. I assume this is default
platform
behaviour, but I think this library is suited to handle this error too.