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 🙏

© 2025 – Pkg Stats / Ryan Hefner

limited-process

v0.1.0

Published

Safely run code in separate process. Limit child process requiring module

Readme

limited-process

Safely run code in separate process. Limit child process requiring module.

npm install --save limited-process

class constructor

constructor(fileName[, jsCode])

fileName : Js file`s absolute path. If you provide jsCode parameter, the fileName will be this code`s alias, use for stack trace.

jsCode : A javascript code string, it will be run in other process.

class properties

  • fileName: jsCode correspond filename, use for stack trace.

  • jsCode: A javascript code string, it will be run in other process.

  • requireList: A module name array, in child process all those module names will be required and exposed at global.lp.requireList.

  • service A object consist of function, child process can use global.lp.invoke to invoke those functions. Note than, those function can not return a function. If you need running a async task, you can return a promise object.

  • cpuUsage Child process cpu usage. If child process is not running, this property will be undefined.

  • memoryUsage Child process memory usage. If child process is not running, this property will be undefined.

  • errors: A array consist of child process uncaught exception.

  • isRunning: Indicates whether the child process is running.

  • startTime: Child process start time.

  • invoke: you can use this to invoke child process global.lp.service. Like this, invoke(functionName[,...args]) or invoke.functionName([...args]).

  • pid, stderr, stdin, stdout: Same to child_process module

class methods

  • async start(option = {debug: false}): Start child process.
    • debug: Is using --inspect flag to run child process. If debug is true, start() will return a debug net address string.
  • setTimeout(delay) How much time to turn off the child process
  • async kill([signal]) The child.kill() methods sends a signal to the child process. If no argument is given, the process will be sent the 'SIGTERM' signal. Before child process close, child process`s global.lp.onClose will be triggered.

class events

  • childProcessError: When child process generate a uncaught exception.
  • close, error, exit: Same to child_process module