fix: avoid null check on signal as it is optional

[mertmit]

Our processes started hanging suddenly throwing port in use error on code changes (graceful restart)
I found out recent update introduced a bug which checks optional parameter and prevents killing the process.

Ref: nocodb/nocodb#10507

This was hard to debug, so I would recommend publishing this when possible.

[atassis]

Sorry for the inconvenience, version 0.2.2 is published with the patch.
I have nothing to test this on, can you double check that npm version is working?

[sergiupris]

@mertmit in this case it's not working as intended using signal: false
In your case using autoRestart you could simply add signal - true:

        autoRestart: true,
        signal: true,

Now, signal false will have no benefit and we always do a restart. Having autoRestart: false will break HMR e.g https://docs.nestjs.com/recipes/hot-reload#configuration is no longer valid documentation (not working)

@atassis

[mertmit]

@sergiupris
I think culprit here is not the signal but extra _stopServer call (line 72) regardless of autoRestart (asking for extra property signal to allow default behavior wouldn't make sense imo)