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

wasm-game-ts

v1.0.0

Published

Browser-first TypeScript framework for running a deterministic WASM game runtime in a WebWorker and rendering via OffscreenCanvas.

Readme

wasm-game-ts

Browser-first TypeScript framework for running a deterministic WASM game runtime in a WebWorker and rendering via OffscreenCanvas.

What it expects from the WASM module

Exports (WASM -> host):

  • init(random_seed: i32, module_hash: i32) -> i32 (HostState* offset)
  • update_start(input_bytes: i32) -> i32 (returns ptr for host to write inputs)
  • update_end(render_for_player: i32) -> void (process + produce render/audio/debug buffers)

Imports (host -> WASM):

  • env.get_file_bytes(id: i32, ptr: *mut u8) -> usize

Render command buffer

The worker renders a binary command buffer written by WASM. Command ids and layouts are defined in: src/worker/renderer.ts

Rust should match these ids and field layouts exactly.

Local demo

  1. Build dist:
npm install
npm run build

Run the dev server:

npm run dev

Open:

http://localhost:5173/demo/index.html

Click "Pick Package Folder" and select a folder containing:

  • your .wasm (built from your Rust code)
  • any assets you want (manifest is generated automatically by the folder picker)

The demo will start the game and stream keyboard/mouse input for player_id=1.


Commands to run

From wasm-game-ts/:

npm install
npm run build
npm run dev
# open http://localhost:5173/demo/index.html