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

forcefield-wasm

v0.2.0

Published

wasm-bindgen bindings for the forcefield simulation: positions exposed as a zero-copy Float64Array view

Readme

forcefield-wasm

wasm-bindgen build of forcefield, a Rust port of d3-force with tick-for-tick parity against the JS reference. Positions, velocities and pins are Float64Array views onto wasm memory: no per-tick copy.

import init, { Simulation } from 'forcefield-wasm'
await init()
const sim = Simulation.fromPositions(Float64Array.of(0, 0, 10, 3, NaN, NaN)) // NaN = spiral init
sim.forceManyBody('charge', [-30], 0.9, 1, Infinity)          // length-1 array = constant
sim.forceLink('link', Uint32Array.of(0, 1), Uint32Array.of(1, 2), [30], [], 1)
sim.tick(1)
const pos = sim.positions()   // [x0, y0, x1, y1, …] view; re-fetch after any non-tick call

Custom JS forces: sim.forceCustom(name, (alpha, pos, vel, fix) => …), called each tick with fresh views; do not call the simulation from inside it. For cytoscape.js use cytoscape-forcefield.

Beyond d3, there are two native additions:

  • sim.forcePairOrder(name, lefts, rights, gap, strength) keeps index pairs apart along x;
  • sim.setCooling(adaptive, alphaDecay, movementThreshold) switches between d3's fixed decay and movement-gated cooling (isAdaptive() reads which is on). Full API in forcefield.d.ts. BSD-3-Clause; derivative of d3-force (Mike Bostock).