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 🙏

© 2025 – Pkg Stats / Ryan Hefner

d3-force-webgpu

v3.1.2

Published

Force-directed graph layout using velocity Verlet integration with WebGPU acceleration.

Readme

d3-force-webgpu

GPU-accelerated force-directed graph layout using WebGPU compute shaders.

This module extends d3-force with WebGPU acceleration, providing 10-100x speedup for large graphs while maintaining full API compatibility.

Features

  • WebGPU Compute Shaders: Force calculations run entirely on the GPU
  • Drop-in Replacement: Same API as forceSimulation, just use forceSimulationGPU
  • Automatic Fallback: Falls back to CPU if WebGPU is unavailable
  • All Forces Supported: Many-body, link, collision, center, x, y, and radial forces

Installation

npm install d3-force-webgpu

Usage

import {
  forceSimulationGPU,
  forceManyBody,
  forceLink,
  forceCenter,
  checkWebGPUSupport
} from 'd3-force-webgpu';

// Check WebGPU availability
const gpuAvailable = await checkWebGPUSupport();
console.log('WebGPU:', gpuAvailable ? 'enabled' : 'CPU fallback');

// Create GPU-accelerated simulation
const simulation = forceSimulationGPU(nodes)
  .force('charge', forceManyBody().strength(-30))
  .force('link', forceLink(links).distance(30))
  .force('center', forceCenter(width / 2, height / 2))
  .on('tick', render);

// Wait for GPU initialization
await simulation.gpuReady();

// Start simulation
simulation.restart();

API

forceSimulationGPU([nodes])

Creates a new GPU-accelerated simulation with the specified array of nodes. This has the same API as forceSimulation with additional methods:

simulation.isGPUEnabled()

Returns true if WebGPU acceleration is active.

simulation.gpuReady()

Returns a Promise that resolves when the GPU is initialized and ready.

checkWebGPUSupport()

Returns a Promise that resolves to true if WebGPU is available.

isWebGPUAvailable()

Synchronously returns true if the WebGPU API exists (doesn't check adapter availability).

Browser Support

WebGPU is supported in:

  • Chrome 113+ (Windows, macOS, ChromeOS)
  • Edge 113+
  • Firefox Nightly (behind flag)
  • Safari Technology Preview

For unsupported browsers, the simulation automatically falls back to CPU computation.

How It Works

The simulation uses WebGPU compute shaders to parallelize force calculations:

  1. Many-Body Force: Tile-based N-body algorithm with O(n²) complexity but massive parallelization across GPU cores
  2. Link Force: Per-node parallel computation of spring forces
  3. Collision Force: Tile-based collision detection with GPU-accelerated overlap resolution
  4. Integration: Parallel position updates with velocity Verlet

Node data is stored in GPU buffers and synced back to JavaScript only when needed for rendering.

Original d3-force

This module is based on d3-force by Mike Bostock.

Resources

License

ISC