why-is-node-running

npm

active

The latest release is less than 12 months old.

why-is-node-running last released 3.2.3 on 2026-10-09. Its latest version requires Node.js >=20.11.

Facts

Latest release
3.2.3, (15 days ago)
First published
(10 years ago)
Releases in the last 12 months
1
Median days between releases
355
Median days between major versions
1,536
Monthly downloads
439,957,551
License
MIT
Source
registry.npmjs.org (checked 2026-10-19)

Major versions

3 major versions have been published.

MajorFirst versionFirst releasedLatest versionLatest released
33.0.02024-07-083.2.32026-10-09
22.0.02018-02-142.3.02024-07-08
11.0.02016-02-091.2.32017-10-18

Runtime requirements

The latest version of why-is-node-running declares these runtime constraints.

RuntimeConstraintMinimum versionSince versionSince
Node.js>=20.1120.11.03.0.02024-07-08

Supported runtimes

The latest version of why-is-node-running runs on 6 tracked runtime releases.

RuntimeCycleReleasedEnd of lifeLTS
Node.js262026-05-052029-04-30yes
Node.js252025-10-152026-06-01
Node.js242025-05-062028-04-30yes
Node.js232024-10-162025-06-01
Node.js222024-04-242027-04-30yes
Node.js212023-10-172024-06-01

Keelbench tracks end-of-life dates for 469 products, updated daily. Check your repositories against these dates with Deps.