Back to Explore

simonepri/pidtree

GitHub
2 updates · last 90 days1 watchersOpen source

Last release:

pidtree is a cross-platform Node.js tool that returns the children process IDs for a given PID, with options to include the root PID, include PPID details, or list all processes. It also provides a CLI to display a process tree in the terminal, optionally outputting results as a list similar to pgrep.

Project status

  • Actively maintained, with a recent update on 2026-06-08, including a major v1.0.0 rewrite and earlier updates the same day, suggesting the project is actively evolving rather than dormant.
  • Apparent update cadence is clustered in 2026-06-08 (v1.0.0 and v0.6.1 on the same date), but there is a long earlier gap, since the previous tagged update noted is v0.6.0 from 2022-06-05.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v1.0.0

    This release is a major 1.0.0 rewrite of pidtree as a pure ESM package and raises the supported runtime to Node.js >= 18. The implementation was refactored from CommonJS modules to ESM imports/exports, with internal parsing logic centralized in a new parse module.

    Breaking
  • v0.6.1

    v0.6.1 improves Windows process enumeration by adding a fallback to PowerShell when the wmic binary is missing. The release notes describe only that user-visible behavior change. The code diff also includes an internal change to how spawn errors are propagated, plus new parsing and unit tests for the fallback path.

  • v0.6.0

    Release v0.6.0 has essentially no human-readable release notes beyond a link to a compare view. The code diff shows mainly internal refactors (platform module resolution, CI wiring) plus a targeted change in how stderr output is handled during process spawning, which affects whether the library throws errors.

  • v0.5.0

    Release v0.5.0 updates the package version from 0.4.0. The provided release notes do not describe any functional changes beyond a compare link, so the actual code modifications must be inferred from the diff.

  • v0.4.0

    Release v0.4.0 is published, but the provided release notes contain no human-readable change log details beyond a link to a GitHub compare view. No information is available here to determine new features, breaking changes, bug fixes, security updates, or migration requirements.