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

gridmash

v0.0.2

Published

components for reconciling grids of scalar values

Readme

gridmash

Node.js CI

components for reconciling grids of scalar values

Note: Project is unstable and extremely early phase

Purpose

gridmash is designed for reconciliing grids of values in a user-definable and predictable way.

Components

|Component | Implemented | PR | Issue | |:---------|:-----------:|:--:|:-----:| |Grid |✔️ |- |- | |Cell |✔️ |- |- |

Installation

npm install gridmash

API Overview

Basic Rendering

The following example shows how to use Grid and Cell to render a reconciler.

<Grid /> will map arrow key press events to reconciliations in the grid between two viable cell values.

A reconciliation is defined by props.reconcile, and occurs when two cell values fulfill props.reconciliationCondition and are in the motion-dependant path of one another.

Grid does not have internal state. It assumes that any reconciliation it identifies should be passed back into its data prop if it is desired to have Grid update with new cell values.

import * as React from "react";
import {
    Grid,
    GridModel,
    Scalar,
    Cell,
} from "gridmash";

interface Props {}

export default (props: Props): React.ReactElement => {
    const [data, setData] = React.useState<GridModel<Scalar>>([
	[0, 0, 0],
	[0, 0, 0],
	[0, 3, 3],
    ]);
    return (
	<Grid
	    // 2d array of scalar values that each cell should hold.
	    data={data}
	    // How each inner value should be rendered.
	    cell={(value: Scalar, key: string) => {
		return (
		    <Cell
			value={value}
			key={key}
			style={{
			    display: "inline-block",
			    padding: "20px",
			}}
		    />
		);
	    }}
	    // The operation to perform between two cells when they reconcile.
	    reconcile={(a, b) => a + b}
	    // What must be true about a cell in order for it to reconcile.
	    reconciliationCondition={a => a % 2 === 0 && a !== 0}
	    // What to do when a reconciliation is found.
	    onReconciliation={(reconciliation) => {
		console.log(reconciliation);
	    }}
	/>
    );
}

Mapping Custom Input Keys

Grid can accept a keyMap prop which allows you to define what events should be mapped to which directions of movement in the grid.

import {
    Grid,
    Motion,
} from "gridmash";

interface Props {}

export default (props: Props): React.ReactElement => {
    // This is the default mapping which relates motions to keydown events.
    const keyMap = new Map([
	[Motion.UP, "ArrowUp"],
	[Motion.DOWN, "ArrowDown"],
	[Motion.LEFT, "ArrowLeft"],
	[Motion.RIGHT, "ArrowRight"],
    ]);
    return (
	<Grid
	    data={[[]]}
	    keyMap={keyMap}
	/>
    );
}