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

collisionwasm

v1.0.6

Published

Simple but very useful image collision check written in Rust which is compiled to WebAssembly.

Readme

CollisionWASM

Pixel-perfect collision detection in the browser using WebAssembly.

Installation

npm install collisionwasm

Usage

You can check the demo in the demo/ folder or at https://oguzhanumutlu.com/collisionwasm/demo/.

First import the Sprite class from the package:

import {Sprite} from "collisionwasm";

Creating a Sprite

If you have the path or the URL of the sprite image, you can create a Sprite instance like this:

const sprite = Sprite.fromPath("./sprite.png");

// Since it takes time to load the image from an external source,
// you can use the `wait` method to wait for the image to be loaded.
// If you render immediately, it will just render a blank sprite.
// Although if you render inside a `requestAnimationFrame` loop, it will work fine.
await sprite.wait();

If you have an Image or Canvas instance you can create a Sprite instance like this:

const sprite = Sprite.fromImage(image);

If you have an ImageData instance you can create a Sprite instance like this:

const sprite = Sprite.fromData(imageData);

Rendering a Sprite

You can simply use the draw method to render the sprite on a CanvasRenderingContext2D:

const canvas = document.getElementById("canvas");
const ctx = canvas.getContext("2d");

let x = 100, y = 100;

sprite.draw(ctx, x, y);

Collision Detection

To check if two sprites are colliding, you can use the collidesWith method:

const sprite1 = Sprite.fromPath("./sprite1.png");
const sprite2 = Sprite.fromPath("./sprite2.png");

await Promise.all([sprite1.wait(), sprite2.wait()]);

const isColliding = sprite1.collidesWith(sprite2, x1, y1, x2, y2);

if (isColliding) {
    console.log("Sprites are colliding!");
} else {
    console.log("Sprites are not colliding.");
}