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

@mkbabb/csp-solver-wasm

v0.2.0

Published

WebAssembly bindings for csp-solver — isomorphic mirror of the Python binding.

Readme

csp-solver-wasm

WebAssembly bindings for csp-solver, exposing the discrete CSP / COP API to JavaScript and TypeScript consumers. The binding is an isomorphic mirror of the Python binding in csp-solver/src/py.rs — same surface, same method names, same argument orders, different binding mechanism.

Build

cd csp-solver/wasm
make wasm

This invokes wasm-pack build --target web --release --out-dir pkg, producing the following artifacts in pkg/:

  • package.json — npm manifest, name csp-solver-wasm
  • csp_solver_wasm.js — ES-module loader, the JS entry point
  • csp_solver_wasm_bg.wasm — the compiled WebAssembly binary
  • csp_solver_wasm.d.ts — TypeScript declarations for every export

Consume

npm install file:../path/to/csp-solver/wasm/pkg
import init, { Csp, SolveConfig, Pruning, Ordering } from "csp-solver-wasm";

await init();

const csp = new Csp();
const a = csp.addVariable(new Uint32Array([1, 2, 3]));
const b = csp.addVariable(new Uint32Array([1, 2, 3]));
csp.addNotEqual(a, b);
csp.finalize();

const cfg = new SolveConfig();
cfg.pruning = Pruning.AC_FC;
const solutions = csp.solve(cfg);

API surface

Two layers, both exported from the same module:

  • Low-level isomorphic mirrorCsp, SolveConfig, SolveStats, and the Pruning / Ordering / PropagationStrategy / OptimizationMode enums. These are line-for-line equivalents of the same names in csp-solver/src/py.rs. The Csp wrapper holds a csp_solver::Csp<BitsetDomain> internally, matching the Python binding's domain choice.

  • Convenience surfacesolveAssignmentCop for bipartite assignment / COP problems. Lands in a future commit; the scaffolding is here so the API can grow without churning the published surface.

Layout

csp-solver/wasm/
├── Cargo.toml         # cdylib + rlib member, path-deps the parent
├── Makefile           # `make wasm` / `make docs` / `make clean`
├── README.md          # this file
├── CHANGELOG.md       # release notes
├── src/
│   ├── lib.rs         # panic-hook init + module re-exports
│   └── isomorphic.rs  # the py.rs mirror
└── pkg/               # wasm-pack output, committed alongside source