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

runaway

v0.1.3

Published

Stop most hogging CPU process when CPUs are pegged

Downloads

3

Readme

runaway

Kill runaway CPU hogging process. Checks the system every minute, and if uptime reports > .90 CPU in last minute, kills the highest CPU process.

Global

$ npm runaway -g
$ runaway

Local

$ npm runaway
$ node runaway &

####Options

Check every n minutes instead of 2

$ checkevery=10 node runaway &

Show all details to console.log

$ debug=1 node runaway &

Write all details to log.txt file

$ debuglog=1 node runaway &

####Testing

Runaway uses nodejs, no additional modules, and system commands uptime, and ps, standard Linux/Unix biz, but doesn't work on Windows.

$ node badprocess

Is an infinite loop and simulates a process gone wrong. If you run it, then run runaway, after about a minute or so, runaway should catch it and kill badprocess.

BEWARE - badprocess spins up a CPU core to the max, so be careful on important or shared systems!