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

hoja

v0.0.3

Published

yet another simple, independent testing framework (TDD like)

Readme

hoja - yet another simple, independent testing framework (TDD like)

Contents

WIP

  • Minimal testing framework designed with declarative syntax for test descriptions and an imperative syntax for execution flow.

  • The main motivation was the need to run specs on different / limited JavaScript engines such as rhino, V7,o ld browsers.

  • Supports synchronous text execution.:

    • It's physically divided on two implementations, synchronous and asynchronous, on purpose since it was used on non asynchronous - non hackeable - JavaScript environments.
  • The assertion syntax is similar to jasmine / mocha based on describe(), expect(), it()..

  • But the execution flow is different, you explicitly stop / start groups of specs imperatively.

  • aims to be as portable, simple and fast.

  • basic support for reports but customizable. The objective is to be agnostics on the report output mediums so we limit to plain text.

  • for the server and the browser.

  • other scenario that shows to be useful is while bundling scripts to be runnel individually bu puppeteer os similar headless, in which case you need to be as fast as possible and a text report to stdout is enough.

Usage

npm install -D canto

API

  • The flow is driven, imperatively, via the object SpecRunner. You declare your tests, and execute them using it:
import { SpecRunner, describe, it, expect, skip, fai } from 'hoja'

reset()
describe('Fruit', () => {
  it('can be eaten', () => {
    expect([1, 2, 3]).toContain(2)
  })
  it('can walk', () => {
    expect('asdas').toContain('as')
    expect(Math.random() > 2).toBe(true)
  })
})
const { results } = run()   // run the inner describe statements. Default implementation is synchronous.

                            // ... ahead in time...
reset()                     // make sure the next execution block is clean.
describe('d1', () => {
  it('must fail', () => {
    expect(1).toBe(1)
    if (1 < 2) {
      skip('Preconditions failed')  // skip() makes the test not to fail nor not to success. 
    }                               // means conditions for the test to execute are not meet in the current environment.
    expect(2).toBe(2)
  })
  it('must not fail2', () => {
    expect(1).toBe(1)
    if(foo()){
      fail('Expected something')
    }
  })
})
const {results, timings} = run({random: true, breakOnFirstError: true})       
                             // this time run() is configured  and returns timing data.

run()

Returns a result object

TODO

  • [ ] api docs
  • [ ] fit(), fdescribe()
  • [ ] make describes optional and introduce test() like ava / jest
  • [w] easy framework to run the tests and descendt report with jsdom and puppetter.
  • [ ] should we invest on optimize performance ?
  • [ ] Issue : Reporter should be named "Renderer" and there should be another type "Reporter"
  • [x] async api