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

type-unit

v1.0.3

Published

TypeScript testing framework. Inspired by XUnit.

Readme

type-unit

TypeUnit enables you to write TypeScript tests in the style of xUnit. It's a simple library that sprinkles syntactic sugar atop your test framework of choice. TypeUnit works by way of plugins, which provide the functionality for actually running the test suite. An example is type-unit-mocha.

Changelog

Version 1.0.0:

  • Version 1.0.0 introduces a plugin system, and the first plugin is type-unit-mocha. Consequently, type-unit itself is no longer reliant on mocha.
  • The suite, fact, and theory decorator names are now lowercase by default (of course, you can alias them upon import if needed: import {fact as Fact} from "type-unit").
  • Updated example to use preferred ES6-style import syntax.

Building

  • Clone this repository.
  • Run npm i.
  • Run npm run build.
  • To execute the tests, install mocha globally (npm i -g mocha), then run npm run test.

Writing a test suite.

  • In your test project, install a TypeUnit plugin (npm i type-unit-mocha --save).
  • Create a typeunit.config.js file:
var mochawrapper = require("type-unit-mocha");
module.exports = {
    plugin: mochawrapper
};
  • Configure your TypeScript project to allow decorators. As of TypeScript 1.5.*, you must set the experimentalDecorators compiler option to true.
  • A class comprises a @suite of tests, and an individual test function is a @fact. A test to run with a series of different parameters is a @theory.
  • How you execute your test runner will depend on the plugin used. In the case of type-unit-mocha, ensure that mocha is installed globally (npm i -g mocha), then run mocha from the same directory as the typeunit.config.js file.

Examples

import {fact, theory, suite} from "type-unit";
import * as assert from "assert";

@suite("Arithmetic")
class MathTests {

    @fact("Should be able to add")
    addition() {
        assert.equal(1 + 1, 2);
    }

    @theory([
      [2, 1, 2],
      [2, 2, 4],
      [2, 3, 8]
      ], "Should be able to exponentiate")
    exponentiation(base: number, exponent: number, expectedValue: number) {
       assert.equal(Math.pow(base, exponent), expectedValue);
    }
}

To do

The following features are on the roadmap

  • Support for decorators that correspond to mocha's beforeEach() and afterEach() and to xUnit Fixtures.
  • Support for alternative test frameworks like jasmine-node or vows.

Contributing

  • Contributions welcome. New features should be tested by adding unit tests file (tests folder). Tests can be executed by running mocha from the root TypeUnit directory, or npm run test.