Here is a example how I start debugger for listening new connections:

@Get('/signal/:signal')
async makeSignal(@Param('signal') signal: string) {
  process.kill(process.pid, signal);
}

If endpoing receives SIGUSR1 signal then debugger is started.
Would be nice if we have another COOL_SIGNAL to stop debugger.

You can use the open() and close() methods from require('inspector') to start and stop the debugger manually.

An additional NodeJS reserved signal should be ideal to stop listenning debugger.

I don't think there are any general purpose signals left for node to claim. SIGUSR2, for example, is in use by at least two popular modules.

You can use the open() and close() methods from require('inspector') to start and stop the debugger manually.

An additional NodeJS reserved signal should be ideal to stop listenning debugger.

I don't think there are any general purpose signals left for node to claim. SIGUSR2, for example, is in use by at least two popular modules.

Then I am curious to know what are use cases to use SIGUSR1 or inspector module?
When to use SIGUSR1 and when to use inspector

The inspector module is for programmatic access to the debugger, what you are doing. SIGUSR1 is for non-programmatic access.

"SIGUSR1" can work in the following situations:
while(1) {}.

"SIGUSR1" can work in the following situations: while(1) {}.

Thanks @theanarkh. This is a great example of SIGUSR1 usage.