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

toplevelprocess

v1.0.0

Published

Node.js add-on for determining the top level process when using child_processes.

Downloads

2

Readme

TopLevelProcess

This utility library address a deficiency in node core as it relates to identifying whether or not a process was launched by a parent node process via child_process.spawn() or child_process.fork().

If you are interested you can read the original feature request to the node team here or see the pull request here in order to learn about the very good reasons why this was not included in node core.

Installation

Installation is pretty standard...

npm install TopLevelProcess

Usage

This utility augments the existing node process and child_process objects. To use, simply require in any node process.

require("TopLevelProcess");

Once required, any usage of child_process.spawn() or child_process.fork() will correctly identify itself as having a parent node process to the spawned/forked process.

Also once required, process.isTopLevelNodeProcess() will be available and will return true if the node process was started as a top level process or if it was a spawn/fork from a upstream node process.

Caveats

With regards to child_process.exec() and child_process.execSync()... exec is different from spawn/fork and does not really seem to fit the same paradigm for this utility.