npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

pidtree-more

v0.2.0

Published

Cross platform children list of a PID based on the work of Simone Primarosa

Downloads

8

Readme

Synopsis

This fork just that add to pidtree the opportunity to have the name of the process and to search with the process name, especially on Windows (not tested on other platforms). It's a base module that help me implements pidtree-watcher (on npmjs)

Usage

var pidtree = require('pidtree');

// Get childs of current process
pidtree(process.pid, function (err, pids) {
  console.log(pids);
  // => []
});

// Include the given pid in the result array
pidtree(process.pid, {root: true}, function (err, pids) {
  console.log(pids);
  // => [727]
});

// Get all the processes of the System (-1 is a special value of this package)
pidtree(-1, function (err, pids) {
  console.log(pids);
  // => [530, 42, ..., 41241]
});

// Include PPID in the results
pidtree(1, {advanced: true}, function (err, pids) {
  console.log(pids);
  // => [{ppid: 1, pid: 530}, {ppid: 1, pid: 42}, ..., {ppid: 1, pid: 41241}]
});

// If no callback is given it returns a promise instead
const pids1 = await pidtree(1);
console.log(pids);
// => [141, 42, ..., 15242]

// you can also search a process by name
const pids2 = await pidtree("firefox");
console.log(pids);
// => [13899, 13900, ..., 15242]


// or with like to search by regexp
const pids3 = await pidtree(-1,{like:"firef"});
console.log(pids);
// => [13899, 13900, ..., 15242]


// you can also search a process by with like
const pids4 = await pidtree(-1,{like:"firef", withNames: true});
console.log(pids);
// => [{pid:13899, name:"firefox.exe"}, {pid:13900, name:"firefox.exe"}, ..., {pid:13913, name:"firefox.exe"}]

// note that searching with option withNames implies with root
const pids5 = await pidtree("myApp",{withNames: true});
console.log(pids);
// => [{pid:13899, name:"myApp"}]

Authors

See also the list of contributors who participated in this project.

License

This project is licensed under the MIT License - see the license file for details.