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

@vaclav-purchart/js-test

v1.1.0

Published

Simple, zero-dependency test framework inspired by mocha and jest.

Readme

@vaclav-purchart/js-test

Simple, zero-dependency test framework inspired by mocha and jest.

Test framework which allows to run both synchronous and asynchronous tests and to structure them into test suites.

Usage

ES6 modules

import { describe, test, assert } from '@vaclav-purchart/js-test'

describe('my test suite', () => {
	test('my async test', async () => {
		const response = await fetch('https://github.com')
		assert.equals(response.status, 200, 'should return HTTP 200 status')
	})
})

CommonJS modules

const { describe, test, assert } = require('@vaclav-purchart/js-test')

describe('my test suite', () => {
	test('my async test', async () => {
		const response = await fetch('https://github.com')
		assert.equals(response.status, 200, 'should return HTTP 200 status')
	})
})

Test definition API

Test suite definition

Test suite can be defined with describe (alias suite).

describe(name, handler)
  • name - string - text identifier of the suite

  • handler - function - sync or async function to init/define the test suite

Test case definition

Test case can be defined with test (alias it).

test(name, handler)
  • name - string - text identifier of the suite

  • handler - function - sync or async function to init/define the test suite

Library API

  • setReporter - function(string) - to print test results (default console.log)
  • globalBefore - function(handler) - sync/async handler to perform action before all tests/suites
  • globalAfter - function(handler) - sync/async handler to perform action after all tests/suites have ended

Example:

import {setReporter, globalBefore, globalAfter} from '@vaclav-purchart/js-test'

setReporter(sendTestResults)

globalBefore(async () => {
	await setupDbConnection()
})

globalAfter(async () => {
	await teardownDbConnection()
})

// ... test definitions

Assertion library

js-test contains very simple assertion library (subset of chai.assert).

  • equal - (realValue, expectedValue, [failedMessage]) - compares given values by strict equality check (===).
  • deepEqual - (realValue, expectedValue, [failedMessage]) - deeply compares all nested values and all have to match. It is not able to compare cyclic objects.
  • isTrue - (expression, [failedMessage]) - compares if the given expression has truthy value (Boolean(value) === true)
  • isFalse - (expression, [failedMessage]) - compares if the given expression has falsy value (Boolean(value) === false)
  • fail - ([failedMessage]) - will always fail

CLI interface

It is possible to run multiple test files by following command:

js-test [my-test-cjs-file.js] [my-test-es6-file.mjs]

(Mixing of CommonJS and ES6 modules is supported.)

TODO

  • make reporters better (info, error, etc.)
  • implement async timeouts