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

performance-harness

v0.1.0

Published

A wrapper for node that captures cpu profiles, gc information and heap dumps

Downloads

6

Readme

A harness for starting a node app and recording performance.

Installation

$ npm install -g performance-harness

Running

$ node-perf run [--out=<path>] <script>

This will run the given script but wrap it in memwatch and a profiler. You can cause a heap dump to be taken by signalling SIGALRM. The internal node process running your code can be exitted by signalling SIGUSR2.

Providing --out will dump the report into the given path rather than ./out.json

The script provided should be the usual entry point into your application that you would run with node <script>.

$ node-perf view <json>

This will start a webserver on port 3000 and expose an html interface to view the results stored in the report json.