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

@elitjs/test

v4.0.4

Published

Test runner, runtime, reporter, and coverage for Elit

Readme

@elitjs/test

Jest-based test runner integration for Elit projects. Extracted from elit as a standalone package.

Install

npm install @elitjs/test

Usage

elit test --run                     # run everything once
elit test --run --file ./testing/unit/my.test.ts

Retries

Flaky tests are retried before being reported as failed — hooks re-run per attempt:

elit test --run --retries 2

Or in elit.config.ts:

export default { test: { retries: 2 } };

Snapshot testing

it('renders the summary', () => {
    expect({ items: 3, sorted: true }).toMatchSnapshot();
});

Baselines live in __snapshots__/<file>.snap.json next to the test file. Object keys are sorted, so key order never breaks a snapshot.

elit test --run                     # compares against baselines
elit test --run --update-snapshots  # (re)records them

Parallel workers

Test files run across worker threads, each with an isolated module registry:

elit test --run --workers 4

Or test: { workers: 4 } in elit.config.ts. Coverage runs fall back to serial automatically.

Run control

elit test --list                  # list matching tests without running
elit test --repeat-each 3         # run every test 3 times
elit test --grep-invert slow      # exclude tests whose names match
elit test --shard 1/3             # CI matrix: run the first third of the files
elit test --pass-with-no-tests    # don't fail when nothing matches

Reporters

elit test --reporter junit        # writes junit.xml for CI ingestion
elit test --reporter html         # writes e2e-report/index.html (open via elit e2e show-report)

webServer & global hooks (elit.config.ts)

export default {
    test: {
        webServer: {
            command: 'elit dev',          // started before the run, stopped after
            port: 5180,
            reuseExistingServer: true,
        },
        globalSetup: './global-setup.ts',      // default export, runs once first
        globalTeardown: './global-teardown.ts',
    },
};

One-shot page capture

elit e2e screenshot http://localhost:5180 home.png --full-page
elit e2e pdf http://localhost:5180 report.pdf
elit e2e open http://localhost:5180

UI mode

Run tests interactively from the browser — file list with checkboxes, run/re-run buttons, and live pass/fail status per test:

elit test --ui            # or: elit e2e --ui [port]

The page polls a local HTTP API (/api/state, POST /api/run), so results stream in as tests finish.

Exit codes

elit test exits non-zero when any test fails, so CI pipelines can gate on it.

License

MIT