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

dry-test-vm

v0.1.0

Published

Dry Test Virtual Machine

Readme

Vagrant VM that runs clean installs of node components, and tests that they work.

For this to work repeatedly, DO NOT install anything outside of npm. We blow away the npm folders before every test. That's how we ensure a clean setup without rebuilding the vm every time.

If you do install something else -- don't -- make sure to remove it cleanly at the end of your test script.

To run:

Install vagrant, and virtual box (follow the instructions on the vagrant page).

then install the binary:

npm install dry-test-vm

run dry-test-vm <path to test script>

It will take a while the first time, it has to provision. It will be faster after the first run. It will leave the VM running.

Run dry-test-vm halt to stop it.

Your test script is a shell script. here is a really simple example I use to test node-tux.

npm install -g node-tux
echo "{}" > .tux.json
tux

That's it. If this was in a shell script in my project directory called "test-tux.sh", I'd run:

dry-test-vm ./test-tux.sh

You can only run one of these tests at a time, because you're using the same virtual machine. Don't try to run two at once.

That's it. Enjoy.