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

lowlife

v0.4.2

Published

An implementation of Conway's Game of Life

Downloads

5

Readme

lowlife

An implementation of Conway's Game of Life. Work-in-progress highly unstable interfaces may change without warning use at your own risk here there be dragons.

Usage

lowlife's data model is based on (immutable) sets of Cartesian coordinate pairs, which represent the locations of all living cells on the grid.

import * as Life from 'lowlife'

//  . O .
//  . . O   glider (origin at top left)
//  O O O

let glider = Life.FromLiving([[1,0], [2,1], [0,2], [1,2], [2,2]])
let iteratedGlider = glider
for (let i = 0; i < 4; i++)
  iteratedGlider = Life.Next(iteratedGlider)

assert(
  JSON.stringify([...Life.Living(iteratedGlider)])
  ===
  JSON.stringify([...Life.Living(glider)].map(([x, y]) => [x + 1, y + 1]))
)

The Next function can optionally reuse a grid's memory when constructing its successor. Any operations on the original grid after using this option will throw an exception:

let glider = Life.FromLiving([[1,0], [2,1], [0,2], [1,2], [2,2]])
let iteratedGlider = glider
for (let i = 0; i < 4; i++)
  iteratedGlider = Life.Next(iteratedGlider, {canFree: true}) // <- Tells `Next` to reuse its argument's memory

assert(
  JSON.stringify([...Life.Living(iteratedGlider)])
  ===
  JSON.stringify([...Life.Living(glider)].map(([x, y]) => [x + 1, y + 1]))
)

This time Living(glider) throws a TypeError. Since iteratedGlider was initially an alias of glider, glider was revoked after the first call to Next

Architecture

Modules, in ascending order of abstraction:

  • branch and leaf provide quadtree operations for their respective subtypes
  • tree assembles them (while applying canonicalization/memoization transforms) to provide full quadtree operations
  • grid embeds a quadtree in the coordinate plane, growing when needed to simulate infinite size
  • life provides memory management