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

bresenham-lighting-engine

v0.2.7

Published

A CPU-based 2D lighting engine using Bresenham's line algorithm with fast native collision detection

Readme

bresenham-lighting-engine

Live Demo NPM Version

What is this madness?

This is an experimental lighting engine that said "nah fam" to GPU shaders and decided to use Bresenham line algorithms for ray casting instead.

The core idea is simple:

  • Cast rays using classic line-drawing algorithms
  • Calculate shadows by checking when rays get yeeted by obstacles
  • Apply light falloff based on distance
  • Render everything with HSV color space because we're fancy like that

Features that might possibly slap

  • Zero GPU dependency - Your integrated graphics can take a nap
  • 🚀 WASM-ready - Runs in browsers without breaking a sweat
  • 📦 Minimalistic AF - No bloated dependencies, just pure algorithmic goodness
  • 🎯 Portable - Will perhaps work in native game engines
  • Performant - Surprisingly fast for CPU-based lighting

Basic Web Usage

This requires a bundler like Vite to wire up the wasm and stuff. Package it with wasm-pack build --target web to get a version that doesn't need bundlers.

import { memory, put, set_collision_mode } from 'bresenham-lighting-engine';

// Initialize collision detection
set_collision_mode(1); // 0=tile-based, 1=pixel-based

// Create a light: id=0, radius=50, x=200, y=100
const lightPtr = put(0, 50, 200, 100);

// Extract pixel data from WASM memory
const lightSize = 50 * 2 + 1; // radius * 2 + 1
const pixelData = new Uint8ClampedArray(
  memory.buffer,
  lightPtr,
  lightSize * lightSize * 4 // RGBA
);

// Render to canvas
const canvas = document.querySelector('canvas');
const ctx = canvas.getContext('2d');
const imageData = new ImageData(pixelData, lightSize, lightSize);
ctx.putImageData(imageData, 0, 0);

Development

Install wasm-pack:

cargo install wasm-pack

Build the WASM module:

wasm-pack build --target bundler

Roadmap (aka "Things I'll Probably Never Do")

  • [x] Basic WASM implementation that doesn't crash
  • [x] Ray casting with proper shadow calculation
  • [ ] Native library bindings (C/C++/whatever)
  • [ ] Godot plugin (because indie devs deserve nice things)
  • [ ] Performance optimizations (SIMD goes brrr)
  • [ ] Better color blending modes
  • [ ] Multi-light support that doesn't melt your CPU