v3.2.0

Notable Changes

Relative file paths

The file paths shown in the output are now relative to the current working directory, if a path is outside of the current working directory the full absolute path will be used instead.

Before

There are 4 handle(s) keeping the process running

# Timeout
/path/to/project/example.js:6  - setInterval(() => {}, 1000)
/path/to/project/example.js:10 - startServer()

# TCPSERVERWRAP
/path/to/project/example.js:7  - server.listen(0)
/path/to/project/example.js:10 - startServer()

# Timeout
/path/to/project/example.js:6  - setInterval(() => {}, 1000)
/path/to/project/example.js:11 - startServer()

# TCPSERVERWRAP
/path/to/project/example.js:7  - server.listen(0)
/path/to/project/example.js:11 - startServer()

After

There are 4 handle(s) keeping the process running

# Timeout
example.js:6  - setInterval(() => {}, 1000)
example.js:10 - startServer()

# TCPSERVERWRAP
example.js:7  - server.listen(0)
example.js:10 - startServer()

# Timeout
example.js:6  - setInterval(() => {}, 1000)
example.js:11 - startServer()

# TCPSERVERWRAP
example.js:7  - server.listen(0)
example.js:11 - startServer()

No more dependencies

This version of why-is-node-running removes all of it's additional dependencies, resulting in a smaller overall package size.

What's Changed

• Add missing permissions to publish workflow by @jonkoops in #72
• Add correct Node.js versions to README by @jonkoops in #73
• Re-write README to better present installation options by @jonkoops in #74
• Update example code to match README by @jonkoops in #75
• Add files field to package.json by @jonkoops in #76
• Remove dependeny on siginfo package by @jonkoops in #77
• Use relative paths for files under current working directory by @jonkoops in #78
• Refactor code to modern JavaScript syntax by @jonkoops in #79
• Replace stackback with internal implementation by @jonkoops in #80

Full Changelog: v3.1.0...v3.2.0