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

protester

v1.0.1

Published

A library + binary for testing Node.js programs using ES modules.

Downloads

2

Readme

Protester

A testing library + binary for Node.js which can handle your ES modules. It uses a different worker for each of your files to prevent hangup and to create (nearly) full isolation. Note that this also means that you can't import anything which utilises parentPort from the worker_threads module. This most probably means your worker files.

Usage

Protester doesn't flood your global object because I find that behaviour quite unpleasant. You have to import the testing functions from the protester package. Example:

import { test } from 'protester'

// You should always use the assert object given here
// because it's hooked into protester.
test('name of the test', assert => {
  assert.equal(true, true)
})

The assert object contains the asserting methods which chai's assert object provides.

Async tests

You can send an async function as a callback in test. It's a good practice to assert the number of assertions in a test. For that, there is an expectedAssertionCount property on the assert object. Example:

import { test } from 'protester'
import { setTimeout as delay } from 'timers/promises'

// You should always use the assert object given here
// because it's hooked into protester.
test('name of the async test', async assert => {
  assert.expectedAssertionCount = 1

  await delay(500)

  assert.equal(true, true)
})

Running the tests

You can simply run protester to run all of your tests and protester [test-file-path] to run a single test. Use protester --help for the complete set of options.

Configuration

Create a protester.config.js in your project's root directory. You can both export your options one-by-one or in a huge object with export default. Check src/default.protester.config.ts for all the options, the default values and the descriptions.