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 🙏

© 2026 – Pkg Stats / Ryan Hefner

jsdom-eval

v0.2.5

Published

eval js inside jsdom for simple testing that requires the dom

Readme

jsdom-eval

eval js inside jsdom for simple testing that requires the dom. if your scripts include a sourcemap, stack traces will point to locations in the original source (great for browserify!)

Usage

jsdom-eval ./my.js --html ./optional.html

or

cat ./my-js | jsdom-eval --html ./optional.html

example using browserify and tape to run dom based tests

browserify ./my_tape_test.js -d | jsdom-eval | faucet

This pipes to faucet because it will correctly set exit codes for tap output. jsdom-eval forwards your console output, but it acts like a browser and does not know anything about exit codes or how to interpret your scripts output.

API

jsdom-eval will either eval code from process.stdin or read the file of the first non flag arument. you may also specify an html file that will be loaded into jsdom with the --html or -H flag.