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

child-process-debug

v0.0.7

Published

Convenience methods for debugging child-process

Downloads

342

Readme

child-process-debug

Convenience methods for debugging child processes in Node.JS. Child processes will be started with --debug if the parent was started with --debug and the children will each get their own increasing port number based off the parent's port number. The default port is 5858. If you add --debug-brk that will also get passed to the children.

Example

var childProcessDebug = require('child-process-debug');

for (var i = 0; i < 4; i++) {
    //if this script wasn't run with --debug this will spawn node example.js [0-3]
    //if this script was run with --debug, this will spawn node --debug=[5859-5862] example.js [0-3]
    childProcessDebug.spawn(['example.js', i]);
}

Methods

spawn([command][, args][, options])

This takes the exact same arguments as child_process.spawn and if the parent had debugging turned on (via --debug), it'll turn on debugging for the spawned child. command is also optional (unlike child_process.spawn) and defaults to process.execPath.

The ChildProcess returned from spawn will have a property called debugPort indicating the debug port chosen for that child or undefined.

fork(modulePath [, args][, options])

This takes the exact same arguments as child_process.fork and if the parent had debugging turned on (via --debug), it'll turn on debugging for the spawned child. Return is the same as spawn above.

nextPort()

Returns the next debug port that comes after the current process's debug port. If the current process doesn't have debug turned on then this will return undefined. This is useful if you're not using spawn and want to specify the --debug=port argument yourself.

exitWithParent(child)

Kill's the spawned child when the parent dies. This will not work if the parent is killed with SIGKILL.

port()

Returns the current process's debug port or undefined if debug is not turned on.

debugBreak()

Returns true if the current process has the flag --debug-brk.

By James Hartig