why-is-node-running

This package is a fork by tbodt with a couple of extra features. You probably shouldn't be using it.

Node is running but you don't know why? why-is-node-running is here to help you.

Installation

Node 8 and above:

1npm i why-is-node-running -g

Earlier Node versions (no longer supported):

1npm i why-is-node-running@v1.x -g

Usage

1const log = require('why-is-node-running') // should be your first require
2const net = require('net')
3
4function createServer () {
5  const server = net.createServer()
6  setInterval(function () {}, 1000)
7  server.listen(0)
8}
9
10createServer()
11createServer()
12
13setTimeout(function () {
14  log() // logs out active handles that are keeping node running
15}, 100)

Save the file as example.js, then execute:

1node ./example.js

Here's the output:

There are 5 handle(s) keeping the process running

# Timeout
/home/maf/dev/node_modules/why-is-node-running/example.js:6  - setInterval(function () {}, 1000)
/home/maf/dev/node_modules/why-is-node-running/example.js:10 - createServer()

# TCPSERVERWRAP
/home/maf/dev/node_modules/why-is-node-running/example.js:7  - server.listen(0)
/home/maf/dev/node_modules/why-is-node-running/example.js:10 - createServer()

# Timeout
/home/maf/dev/node_modules/why-is-node-running/example.js:6  - setInterval(function () {}, 1000)
/home/maf/dev/node_modules/why-is-node-running/example.js:11 - createServer()

# TCPSERVERWRAP
/home/maf/dev/node_modules/why-is-node-running/example.js:7  - server.listen(0)
/home/maf/dev/node_modules/why-is-node-running/example.js:11 - createServer()

# Timeout
/home/maf/dev/node_modules/why-is-node-running/example.js:13 - setTimeout(function () {

CLI

You can also run why-is-node-running as a standalone if you don't want to include it inside your code. Sending SIGUSR1 signal to the process will produce the log.

1why-is-node-running /path/to/some/file.js

probing module /path/to/some/file.js
kill -SIGUSR1 31115 for logging

To trigger the log:

kill -SIGUSR1 31115

License

MIT