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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sdesalas/3d-force-graph

v2.0.10

Published

UI component for a 3D force-directed graph using ThreeJS and ngraph.forcelayout3d layout engine

Downloads

1

Readme

3D Force-Directed Graph

NPM

A web component to represent a graph data structure in a 3-dimensional space using a force-directed iterative layout. Uses ThreeJS/WebGL for 3D rendering and either d3-force-3d or anvaka's ngraph for the underlying physics engine.

Quick start

import ForceGraph3D from '3d-force-graph';

or

var ForceGraph3D = require('3d-force-graph');

or even

<script src="//unpkg.com/3d-force-graph/dist/3d-force-graph.min.js"></script>

then

var myGraph = ForceGraph3D(myDOMElement, { width: 500, lineOpacity: 0.5 });

API reference

| Option | Description | Default | | ------------------ | -------------------------------------------------------------------------------------------------------------------------- | ------------- | | width([px]) | Canvas width | <window width> | | height([px]) | Canvas height | <window height> | | graphData([data]) | Graph data structure (see below for syntax details) | { nodes: [], links: [] } | | jsonUrl([url]) | URL of JSON file to load graph data directly from, as an alternative to specifying graphData directly || | numDimensions([int]) | Number of dimensions to run the force simulation on (1, 2 or 3) | 3 | | nodeRelSize([num]) | Ratio of node sphere volume (cubic px) per value unit | 4 | | lineOpacity([num]) | Line opacity of links, between [0,1] | 0.2 | | autoColorBy([str]) | Node object accessor attribute to automatically group colors by, only affects nodes without a color attribute || | idField([str]) | Node object accessor attribute for unique node id (used in link objects source/target) | id | | valField([str]) | Node object accessor attribute for node numeric value (affects sphere volume) | val | | nameField([str]) | Node object accessor attribute for name (shown in label) | name | | colorField([str]) | Node object accessor attribute for node color (affects sphere color) | color | | linkSourceField([str]) | Link object accessor attribute referring to id of source node | source | | linkTargetField([str]) | Link object accessor attribute referring to id of target node | target | | forceEngine([str]) | Force-simulation engine to use (d3 or ngraph) | d3 | | warmupTicks([int]) | Number of layout engine cycles to dry-run at ignition before starting to render | 0 | | cooldownTicks([int]) | How many build-in frames to render before stopping and freezing the layout engine | Infinity | | cooldownTime([num]) | How long (ms) to render for before stopping and freezing the layout engine | 15000 | | resetProps() | Reset all component properties to their default value ||

Input JSON syntax

{
    "nodes": [ 
        { 
          "id": "id1",
          "name": "name1",
          "val": 1 
        },
        { 
          "id": "id2",
          "name": "name2",
          "val": 10 
        },
        (...)
    ],
    "links": [
        {
            "source": "id1",
            "target": "id2"
        },
        (...)
    ]
}

Local development

npm install
npm run watch