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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@testingrequired/tf

v0.0.23

Published

A testing framework

Readme

tf

Build Status

A testing framework.

Features

Note

This is not a production ready project yet. Breaking changes should be expected.

Getting Started

Install

npm version

$ npm i -D @testingrequired/tf@latest

Supported Node Versions

latest & lts

Executable

The framework doesn't provide an executable so you'll need to create one: ./bin/tf.js

import { run } from "@testingrequired/tf";

run();

Configure

This will do nothing so far. The framework makes zero assumptions about how you want it to behave. Unit testing, mocking, what your test syntax looks like. You will need to define that behavior using middleware in the executable:

import { run, config, middleware } from "@testingrequired/tf";

const { starter, matchTestFiles, specSyntax } = middleware;

run(config(starter, matchTestFiles("./tests/**/*.spec.js"), specSyntax));

A config composes middleware to define that behavior. Here matchTestFiles defines how to find the test files while specSyntax defines how to read the them.

starter is an optional middleware that bundles some of the core middlewares to get you started: randomize test order, run tests, report results and more. Of course you can skip this and define exactly what middleware you wish to use.

Wire Test Script

{
  ...package,
  "scripts": {
    "test": "node -r esm ./bin/tf.js"
  }
}

This example uses esm to support ES modules in your executable.

Write Tests

Create a test file: ./tests/example.spec.js

describe("increment value", () => {
  let value = 0;

  beforeEach(() => {
    value++;
  });

  it("should equal correct value", () => assert(value === 1));
});

Run Tests

$ npm test

Example Project

See a simple implementation: https://github.com/testingrequired/tf-example

Next Steps

Middleware

Look through the growing list of available middleware to build the testing functionality your project needs.

More In Depth

The anatomy documentation explains how the framework is structured and how middleware works. This would be a good place to start if you want to write custom middleware.

Custom Middleware

Define the behavior required to run your tests by writing custom middleware.

Contributing

See development.

Built With