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

@threenative/playtest

v0.1.0

Published

Scenario-driven playtest harness for Three.js games. Runs on plain Three.js with zero ThreeNative dependencies.

Readme

@threenative/playtest

Run a schema-version-1 browser scenario against any development URL:

npx @threenative/playtest playtests/movement.playtest.json \
  --url http://127.0.0.1:5173 --server-command "npm run dev"

Install the bridge from @threenative/playtest/three when semantic entity, camera, movement, or visibility assertions are required. Browser-only input, screenshot, DOM, console, network, and trace evidence does not require an adapter. Run npx @threenative/playtest init to create a config, smoke scenario, and adapter example without changing application source.

Pass chromium flags with --browser-arg, repeated once per flag. A WebGPU target does not start without them:

npx @threenative/playtest playtests/movement.playtest.json \
  --url http://127.0.0.1:5173 \
  --browser-arg --enable-unsafe-webgpu \
  --browser-arg --enable-features=Vulkan

Device targets

The same scenario format runs through --target browser, --target android, or --target ios. An iOS simulator run installs a built app, launches it with simctl, and uses the app data-container mailbox:

npx @threenative/playtest playtests/device-smoke.playtest.json \
  --target ios --app build/threenative-ios.app \
  --bundle-id dev.threenative.runtime --device booted

For a signed physical build, add --ios-transport device --device <devicectl-id>. Network, DOM, and visual-metric assertions are unsupported on device targets and fail TN_PLAYTEST_UNSUPPORTED_ON_TARGET with exit code 2. Default CI does not run Android or iOS device scenarios. .github/workflows/native-platforms.yml is an explicit opt-in platform lane; an absent run is not a pass.

What a passing run means

A scenario only reports pass when at least one assertion was evaluated against an observation that actually arrived. Assertions fail closed: a missing entity, an absent resource, an empty effect log, or a scenario with no assertions at all is a failure, never a silent pass. Wrong-typed assertion values are rejected when the scenario loads rather than dropped, so a scenario cannot quietly run with fewer checks than its author wrote.