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

jsdom-runner

v0.0.3

Published

run browser tests within an emulated DOM

Downloads

7

Readme

jsdom-runner

run browser tests or scripts within an emulated DOM

Usage

This library is intended to run any script from NodeJs inside an emulated DOM provided by jsdom. Script is read from standard input and results are displayed to standard output or standard error by connecting the jsdom console to NodeJs console.

For example Tape results are directed to stdout. Any test library or script writing to the console should work.

Example

test.js:

var test = require('tape');
 
test('demo', function (t) {
	t.equal(1+1, 2)
	t.end()
})

Then build it and run the test:

browserify test.js | jsdom-runner

API

var runner = require('jsdom-runner')

runner(pageOptions, jsdomOptions)

Returns a writable stream. Pipe your js code into it.

  • pageOptions: options for create-html module, documentation is here
  • jsdomOptions: options for jsdom instance, documentation is here

Install

npm install -g jsdom-runner

But --save-dev option should suffice!

Similar projects

  • https://github.com/substack/testling (tests with the browser installed on your system)
  • https://github.com/shama/testron (tests with Electron)
  • https://github.com/rstacruz/jsdom-global (different approach, injects the DOM into the test)