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

@hackbg/runspec

v2.3.1

Published

Test runner.

Downloads

11

Readme

@hackbg/runspec NPM version

Minimal test runner and reporter.

Its gimmick is that there are no gimmicks. No describe, no expect, no beforeEach/afterAll, etc. Who told you you needed those, anyway?

How to use

  1. Define your test cases as plain old functions - synchronous or asynchronous, it's smart enough to handle both correctly, and you're smart enough to use JavaScript's standard control flow vocabulary.

  2. Group test cases into specifications via regular ES modules (i.e. collect them all in an object and export default it.)

// spec1.spec.js
export default {
  'synchronous test' (assert) {
    assert(true)
  },
  async 'asynchronous test' (assert) {
    await someAsyncFunction()
    assert(true)
  }
}
  1. Group specifications into a test suite in a single executable script which calls runSpec on the test suite to execute the specifications. By default, it looks at process.argv.slice(2) - if it's empty, it runs all specs. If it contains names of test suites, it runs only those.
// index.spec.js
import runSpec from '@hackbg/runspec'
import Spec1   from './spec1.spec'
import Spec2   from './spec2.spec'
import Spec3   from './spec3.spec'
runSpec({ Spec1, Spec2, Spec3 })
node index.spec.js
node index.spec.js Spec1
node index.spec.js Spec2 Spec3
  1. Add the script to your project's package.json and run with npm test.
{
  "scripts": {
    "test": "node index.spec.js"
  }
}
npm test
npm test Spec1
npm test Spec2 Spec3