v3.2.2

What's Changed

• Upgrade publication workflow to Node.js 22 by @jonkoops in #83
• Use a WeakRef to store the resource by @betalb in #87

New Contributors

• @betalb made their first contribution in #87

Full Changelog: v3.2.1...v3.2.2

v3.2.1

What's Changed

• Omit stacks with an untracable file name by @jonkoops in #82

Full Changelog: v3.2.0...v3.2.1

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

v3.1.0

What's Changed

• Fix typo in include entrypoint by @jonkoops in #71
• Describe usage of CLI through npx by @jonkoops in #66
• Add type definitions for TypeScript by @jonkoops in #70
• Add GitHub Actions workflow to publish package by @jonkoops in #69

Full Changelog: v3.0.0...v3.1.0

v3.0.0

What's Changed

• Use standard JavaScript modules by @jonkoops in #67

Breaking Changes

This release raises the required Node.js version to 20.11 or higher, and introduces support for standardized JavaScript modules. This makes the package incompatible with CommonJS based environments and is thus a breaking change. If you want to use this version the following changes should be made:

Use JavaScript modules instead of CommonJS

-const why = require('why-is-node-running')
+import why from 'why-is-node-running'

Use --import instead of --require

-node --require why-is-node-running/include /path/to/some/file.js
+node --import why-is-node-running/include /path/to/some/file.js

Full Changelog: v2.3.0...v3.0.0

v2.3.0

What's Changed

• Hide internals from modern Node.js versions by @jonkoops in #65

Full Changelog: v2.2.2...v2.3.0