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

@irtio/testing

v4.4.0

Published

irtio's blessed test API: testRoom() in-process rooms with real client semantics, plus Vitest matchers

Readme

@irtio/testing

Test room logic with real irtio clients and a controllable clock. Check synchronization, RPCs, reconnection, and visibility without opening sockets.

npm install --save-dev @irtio/testing vitest

Test a player update

This test uses the room generated by npx irtio init --tick --yes. Create or replace irtio/room.test.ts:

import { expect, test } from 'vitest';
import { testRoom } from '@irtio/testing';
import '@irtio/testing/matchers';
import room from './room.js';

test('an owned write reaches another player', async () => {
  const t = await testRoom(room);
  try {
    const [a, b] = await t.join(2, { role: 'player' });
    const player = a.state.players.get(a.id);
    expect(player).toBeDefined();
    player!.x = 10;
    a.flush();
    await t.tick(2);

    expect(t.state.players.get(a.id)?.x).toBe(10);
    expect(b.state.players.get(a.id)?.x).toBe(10);
    expect(t).toHaveConverged();
    expect(t).toHaveNoVisibilityLeaks();
  } finally {
    t.stop();
  }
});
npx vitest run irtio/room.test.ts

Drive the clock

| Method | Behavior | | --- | --- | | await t.join(spec?) | Join one client | | await t.join(n, spec?) | Join multiple clients | | await t.tick(n?) | Advance server ticks; defaults to one | | await t.run(ms) | Advance fake time in milliseconds | | await t.until(predicate, options?) | Advance until a condition holds, or reject at the limit | | t.stop() | Stop the room and its clients |

Await all clock operations. By default, awaiting client RPCs also advances the clock until they settle, and a room handler error fails the test. Configure autoPump and failOnHandlerError when testing those behaviors explicitly.

testRelay() tests schema-less relay messaging. Import @irtio/testing/matchers to register Vitest matchers; the main entry point also exports assertion functions for other runners. For physics rooms, await the corresponding initPhysics, initRapier2d, or initMatter initializer before creating the test room.

See the testing reference for all options, matchers, network conditions, and physics helpers.