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

akriunit

v1.0.0

Published

Lightweight and beginner-friendly JS unit testing based on PHPUnit workflow

Readme

Note: This was written only for the purpose of introducing students to the concept of unit testing - please don't use this for any serious projects. Consider packages like Jest instead.

Basic Usage

  1. Ensure you have Node.js v24.0.0 or higher installed on your system.

  2. Install as a devDependency of your project with npm:
    npm i --save-dev akriunit

  3. Create a directory, preferrably in the root of your project, to contain all your test files. Note that akriunit does not search recursively for test files - any and all test files must be flat in the same directory.

  4. In your test files, import TestCase (import { TestCase } from "akriunit"). Use this as the parent of your test class. Note that you may not define your own constructor.

  5. In your test class, write public methods, their names always starting with 'hf' for happy flow or 'ef' for error flow, testing your source methods and assert their outcome using any of the following built-in assertions:

  • TestCase.assertTrue - evaluates a value as equal to true
  • TestCase.assertFalse - evaluates a value as equal to false
  • TestCase.assertEquals - evaluates two values as equal
  • TestCase.assertThrows - asserts that a callback function throws an error, optionally checking against a message
  1. Run npx akriunit {test directory} to run AkriUnit on all tests in the provided directory. You can optionally provide a specific file name as a second argument to run only that test file.

Changelog v1.0.0

  • Added bin script, users can now run the test runner through npx akriunit
  • Replaced 'main' entrypoint field with 'exports'
  • Package entrypoint now exposes TestCase, which can now be imported as easily as import { TestCase } from "akriunit"
  • Removed TestCase.isTruthy
  • Removed TestCase.isFalsy
  • Cleaned up (some of) my lazy code in TestCase & cli
  • Changed published package from raw source to compressed dist