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

@rongjs/test

v0.6.0

Published

A lightweight, engine-neutral JavaScript test framework for Rong

Readme

@rongjs/test

A small, zero-dependency JavaScript test framework for embedded runtimes. It provides sequential async tests, nested suites, hooks, matchers, structured reports, and optional lifecycle events without depending on Node.js APIs, timers, a filesystem, or Rong runtime modules.

import { describe, test, expect } from "@rongjs/test";

describe("URL", () => {
  test("parses the host", () => {
    expect(new URL("https://example.com/path").host).toBe("example.com");
  });
});

const report = await globalThis.__RONG_TEST__.run();

Embedders must evaluate test source first and call run() afterward. Source evaluation only registers cases. The returned report is JSON-compatible, and ordinary case failures resolve in report.cases instead of rejecting run().

Classic-script loading

src/runtime.js has no imports or exports, so an embedder may evaluate it as a classic script before evaluating test source. It installs describe, test, beforeEach, afterEach, and expect as globals. It does not install it.

Host extensions

A host may define this object before loading the runtime:

globalThis.__RONG_TEST_HOST__ = {
  args: { locale: "en" },
  attach: async (name, artifact) => {},
  report: async (event) => {},
};

args and attach become test.args and test.attach. The optional reporter receives case_started and case_finished events. The framework assigns no meaning to host arguments or artifacts.

The host remains responsible for source loading, overall deadlines, interruption/cancellation, console capture, and converting failed cases into a process or protocol status.