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

pulgar

v0.0.11

Published

A test runner with Node.js embedded

Readme

pulgar

a small js test runner with Node.js embedded in a single, simple binary

pulgar running the ms test suite

npx pulgar@latest

why?

the main motivation was to find out whether vitest is really the baseline for node.js test runner performance, and I also wanted to learn jai so things coincided into this project.

vitest is fast, but it's not as fast as the computer can go. javascript itself is not as fast as the computer can go, but even with the bottleneck that javascript can be, current test runners are not bottlenecked by the test code.

usage

pulgar            # runs every test file under the current directory
pulgar parse      # runs files whose path contains "parse"
pulgar ./src/     # runs files whose path starts with src/

arguments are filters on the relative file path. a filter starting with ./ or / anchors to the start of the path, anything else matches anywhere. matching is case-insensitive.

files ending in .test or .spec with .ts, .mts, .cts, .js, .mjs or .cjs are picked up.

there is no config file.

what works

  • describe, test and it, with skip, todo, fails, skipIf and runIf
  • beforeAll, afterAll, beforeEach, afterEach
  • expect with .not, expect.unreachable and expectTypeOf
  • matchers: toBe, toEqual, toStrictEqual, toBeNull, toBeUndefined, toBeDefined, toBeTruthy, toBeFalsy, toThrow, toBeTypeOf, toBeInstanceOf, toBeGreaterThan, toBeGreaterThanOrEqual, toBeLessThan, toBeLessThanOrEqual, toContain, toContainEqual, toHaveLength
  • import { ... } from 'vitest' and import { ... } from '@jest/globals' resolves to pulgar's own api
  • typescript, through node's type stripping. so no enums, namespaces, decorators or jsx
  • extensionless relative imports resolve to .ts, .js or an index file
  • import.meta.url, import.meta.dirname, __filename and __dirname
  • supports linux x64, macOS silicon and win32 x64

see TODO.md.

building from source

you need the jai compiler and a node checkout built as a shared library.

git submodule update --init vendor/node
cd vendor/node && ./configure --shared --ninja && ninja -C out/Release && cd ../..
jai build.jai -optimized

node takes a while to build. on windows use vcbuild.bat dll instead of configure and ninja.