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

@rnd7/rum-tester

v1.0.20

Published

Rumbullion ES6 test-runner

Downloads

2

Readme

rum-tester

Rumbullion ES6 test-runner. Basically a wrapper around mocha

Install

I prefer installation per package. But you can also install it global to link the make-rum command systemwide.

npm i -D @rnd7/rum-tester

Run

Configure it within the package.json file of your project. If present the directory setting in the rum.tester config will define the entry point otherwise it defaults to 'test'.

{
  "name": "myPackage",
  "rum": {
    "tester": {
      "directory": "test"
    }
  },
  "scripts": {
    "test": "test-rum"
  },
  "devDependencies": {
    "@rnd7/rum-tester": "^1.0.0"
  }
}

And afterwards you can run the script using

npm test

Or execute it via npx from your project root, while it still uses the package.json for configuration

npx test-rum

You might also invoke it by poiting node towards the bin js, though it is only recommended for development purposes or to test the rum-tester using rum-tester.

node bin/test-rum.js

License

See the LICENSE file for software license rights and limitations (MIT).