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

inforce

v0.0.10

Published

A simple function based test runner

Downloads

35

Readme

:cop: Inforce

A simple function based test runner. Its not BDD. Does not include an assertion library - only a test collector and test runner.

:package: Install

npm install --dev inforce
or
yarn add --dev inforce

:wrench: Usage

Add as an npm script in package.json.

"scripts": {
  "test": "inforce",
  "test-example": "inforce  --targetPath ./example.test.js",
  "test-verbose": inforce --level verbose
}

:abacus: Options

Check out the main function's params/defaults here.

--targetPath

The relative path to search for tests. Can be directory or file. Deafults to ./src.

--testFileRegex

The pattern to use when filtering test files. Defaults to .*\.test\.js.

-- testFnRegex

The pattern to use when filtering exported functions from test modules. Defaults to ^test.*. If you want to execute all functions exported from a test module -- so you don't have to name test functions with test -- set this to something like .+.

--level

The log level to use.

  • slient: log nothing
  • default: log enough for normal dev use (default)
  • verbose: log lots. helpful for debugging test collection/running not working as you expect
  • debug: log everything. helpful for debugging issues with the inforce project

Example Output

Example Test File

See example.test.js