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

workshopper-verify-processor

v0.0.2

Published

A verify processor that I've used in a few projects.

Readme

workshopper-verify-processor

A verify processor that I've used in a few projects.

Installation

npm install --save workshopper-verify-processor

Usage

Pass the current exercise and a verification function to the output of this module.

const exercise = require('workshopper-exercise')()
const verifyProcessor = require('workshopper-verify-processor')

exercise.addVerifyProcessor(verifyProcessor(exercise, async (test) => {
  await test.notEmpty(aList, 'translation_string', {
    key: 'value'
  })
}))

Your verification function will receive a test argument that is an object with various assertions.

Assertions can take promises as arguments and will return promises too.

The penultimate argument to an assertion is the name of a translation string. A success message will be printed if the assertion is met otherwise an error message will be shown.

pass. or fail. will be prepended to your translation string so you should have a translation file similar to:

{
  // ...
  "common": {
    "exercise": {
      "pass": {
        "translation_string": "This assertion passed with key {{key}}"
      },
      "fail": {
        "translation_string": "This assertion failed with key {{key}}"
      }
    }
  }
}

or per-exercise:

{
  // ...
  "exercises": {
    "an_exercise": {
      "pass": {
        "translation_string": "This assertion passed with key {{key}}"
      },
      "fail": {
        "translation_string": "This assertion passed with key {{key}}"
      }
    }
  }
}

The final argument to the assertion is an object with key/value pairs that are used to do replacements in the translation string.

If an assertion fails, the test is aborted and an error message is shown.

Adding custom validations

To add custom assertions, add them to verifyProcessor.assertions

Any promises passed as arguments to assertion functions will be automatically resolved before the assertion function is called.

Custom assertions can return either a boolean value or a promise that will eventually resolve to a boolean value.

const verifyProcessor = require('workshopper-verify-processor')

verifyProcessor.assertions = Object.assign({}, verifyProcessor.assertions, {
  greaterThanOne: (left) => left > 1
})

Then later:

exercise.addVerifyProcessor(verifyProcessor(exercise, async (test) => {
  await test.greaterThanOne(5, 'translation_string', {
    key: 'value'
  })
}))