NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #745 most downloaded on npm
Node is running but you don't know why? why-is-node-running is here to help you.
Last release 2 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 2.2 years
Some releases are documented
notes for 6 of 24 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
24 releases · first in 2016
Upgrade publication workflow to Node.js 22 by @jonkoops in #83
Omit stacks with an untracable file name by @jonkoops in #82
Full Changelog: v3.2.0...v3.2.1
One column per quarter.
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 a
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()
This version of why-is-node-running removes all of it's additional dependencies, resulting in a smaller overall package size.
files field to package.json by @jonkoops in #76siginfo package by @jonkoops in #77stackback with internal implementation by @jonkoops in #80Full Changelog: v3.1.0...v3.2.0
Fix typo in include entrypoint by @jonkoops in #71
This makes the package incompatible with CommonJS based environments and is thus a breaking change. If you want to use this version the following chan…
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.jsFull Changelog: v2.3.0...v3.0.0
Hide internals from modern Node.js versions by @jonkoops in #65
Full Changelog: v2.2.2...v2.3.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →