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-gaming/jgenesis-wasm

v0.1.1

Published

jgenesis compiled to WebAssembly, with a JS SDK conforming to the wasm-gaming engine contract.

Readme

@wasm-gaming/jgenesis-wasm

Build Release

jgenesis (Rust, wasm-bindgen web frontend) packaged as a wasm-gaming engine SDK.

This subproject follows the same engine-package approach used by rsdkv3 and rsdkv4:

  • typed manifest
  • typed options
  • load(config) engine SDK surface
  • Makefile-driven build (build-sdk, build-wasm, preview)

Contract surface

import { manifest, load } from '@wasm-gaming/jgenesis-wasm';

const engine = await load({
  canvas,
  assets: { rom: romBytes },
  options: { romFileName: 'sonic-1.bin' },
  onEvent: (e) => { /* ready | error */ },
});

engine.reset();
engine.setInput('jgenesis');
engine.destroy();

Build

make build        # WASM + SDK
make build-sdk    # TS only
make build-wasm   # builds jgenesis-web in Docker (local scripts)
make preview      # serves dist/ with COOP/COEP

dist/original and dist/index.html

make build-wasm clones jsgroth/jgenesis, builds frontend/jgenesis-web, and writes:

  • runtime package files to dist/jgenesis/
  • upstream web snapshot to dist/original/:
    • dist/original/index.html
    • dist/original/pkg/
    • dist/original/js/

Then build-demo compiles this package demo shell and writes it to:

  • dist/index.html

build-demo will not overwrite an existing upstream dist/original/index.html.

If build-demo runs before build-wasm, and dist/index.html already exists, it may still be preserved at:

  • dist/original/index.html

Notes

  • WASM build orchestration is local to this repo via scripts/build-docker.sh and scripts/build-jgenesis.sh.
  • ROM files are user-provided and never committed.