Convert Figma logo to code with AI

vasturiano logo3d-force-graph

3D force-directed graph component using ThreeJS/WebGL

4,641
818
4,641
234

Top Related Projects

101,622

JavaScript 3D Library.

Force-directed graph layout using velocity Verlet integration.

7,849

⚠️ This project is not maintained anymore! Please go to https://github.com/visjs

:dizzy: Display dynamic, automatically organised, customizable network views.

Graph theory (network) library for visualisation and analysis

16,856

Open-source JavaScript charting library behind Plotly and Dash

Quick Overview

3d-force-graph is a JavaScript library for creating 3D force-directed graphs using Three.js and d3-force-3d. It provides an easy-to-use API for visualizing complex network data in an interactive 3D environment, with support for custom node/link geometries, animations, and various user interactions.

Pros

  • Easy to use API with sensible defaults for quick graph visualization
  • Highly customizable with support for custom node/link geometries and materials
  • Excellent performance, capable of handling large datasets with thousands of nodes
  • Rich set of features including VR support, anti-aliasing, and particle effects

Cons

  • Steep learning curve for advanced customizations
  • Limited built-in layout algorithms beyond force-directed layout
  • Dependency on Three.js may increase bundle size for smaller projects
  • Documentation could be more comprehensive for some advanced features

Code Examples

Creating a basic 3D force graph:

const Graph = ForceGraph3D()
  (document.getElementById('3d-graph'))
    .graphData(myData)
    .nodeLabel('id')
    .nodeColor('color');

Adding custom node geometries:

Graph.nodeThreeObject(node => {
  const sprite = new SpriteText(node.id);
  sprite.material.depthWrite = false;
  sprite.color = node.color;
  sprite.textHeight = 8;
  return sprite;
});

Implementing click events on nodes:

Graph.onNodeClick(node => {
  // Center view on node
  Graph.cameraPosition(
    { x: node.x, y: node.y, z: node.z },
    node,
    3000
  );
});

Getting Started

  1. Install the library:

    npm install 3d-force-graph
    
  2. Import and use in your project:

    import ForceGraph3D from '3d-force-graph';
    
    const myData = {
      nodes: [{ id: 'node1' }, { id: 'node2' }],
      links: [{ source: 'node1', target: 'node2' }]
    };
    
    const myGraph = ForceGraph3D()
      (document.getElementById('3d-graph'))
      .graphData(myData);
    
  3. Customize as needed using the available API methods.

Competitor Comparisons

101,622

JavaScript 3D Library.

Pros of three.js

  • More comprehensive and flexible 3D library
  • Larger community and ecosystem
  • Supports a wider range of 3D rendering techniques and effects

Cons of three.js

  • Steeper learning curve
  • Requires more code to create basic 3D visualizations
  • Less specialized for force-directed graph rendering

Code Comparison

three.js:

const scene = new THREE.Scene();
const camera = new THREE.PerspectiveCamera(75, window.innerWidth / window.innerHeight, 0.1, 1000);
const renderer = new THREE.WebGLRenderer();
renderer.setSize(window.innerWidth, window.innerHeight);
document.body.appendChild(renderer.domElement);

3d-force-graph:

const Graph = ForceGraph3D()
  .graphData(myData)
  .nodeLabel('id')
  .nodeAutoColorBy('group')
  .linkDirectionalParticles('value');

three.js is a more general-purpose 3D library, offering greater flexibility and control over 3D scenes. It requires more setup code but provides extensive customization options. 3d-force-graph, on the other hand, is specifically designed for creating force-directed graphs in 3D, offering a simpler API for this specific use case. While three.js has a larger community and more resources available, 3d-force-graph provides a more streamlined experience for graph visualization tasks.

Force-directed graph layout using velocity Verlet integration.

Pros of d3-force

  • More flexible and customizable for complex force simulations
  • Part of the larger D3.js ecosystem, integrating well with other D3 modules
  • Lightweight and focused on 2D force-directed layouts

Cons of d3-force

  • Steeper learning curve, especially for those new to D3.js
  • Requires more manual setup and configuration for 3D visualizations
  • Less out-of-the-box functionality for 3D graph rendering

Code Comparison

3d-force-graph:

const Graph = ForceGraph3D()
  .graphData(myData)
  .nodeColor(() => 'red')
  .linkWidth(1);

d3-force:

const simulation = d3.forceSimulation(nodes)
  .force("link", d3.forceLink(links))
  .force("charge", d3.forceManyBody())
  .force("center", d3.forceCenter());

3d-force-graph provides a higher-level API for quick 3D graph setup, while d3-force offers more granular control over force simulation parameters. 3d-force-graph is better suited for rapid 3D graph visualization, whereas d3-force excels in custom force simulations and 2D layouts. The choice between them depends on the specific requirements of the project, such as dimensionality, customization needs, and integration with other D3.js components.

7,849

⚠️ This project is not maintained anymore! Please go to https://github.com/visjs

Pros of vis

  • More comprehensive library with various chart types beyond force-directed graphs
  • Longer development history and larger community support
  • Offers both 2D and 3D visualization capabilities

Cons of vis

  • Steeper learning curve due to more complex API
  • Larger file size and potentially heavier performance impact
  • Less focused on force-directed graphs specifically

Code Comparison

3d-force-graph:

const Graph = ForceGraph3D()
  .graphData(myData)
  .nodeColor(() => 'red')
  .linkWidth(1);

vis:

var nodes = new vis.DataSet(myNodes);
var edges = new vis.DataSet(myEdges);
var network = new vis.Network(container, {nodes, edges}, options);

Summary

3d-force-graph is more specialized for 3D force-directed graphs, offering a simpler API and potentially better performance for this specific use case. vis is a more versatile library with a wider range of visualization options but may require more setup and configuration. The choice between them depends on the specific project requirements and the desired level of customization.

:dizzy: Display dynamic, automatically organised, customizable network views.

Pros of vis-network

  • More mature and established library with a larger community
  • Supports both 2D and 3D network visualizations
  • Offers a wider range of customization options and built-in layouts

Cons of vis-network

  • Steeper learning curve due to more complex API
  • Heavier library size, which may impact load times for smaller projects
  • Less focus on performance optimization for large-scale networks

Code Comparison

vis-network:

var nodes = new vis.DataSet([
  {id: 1, label: 'Node 1'},
  {id: 2, label: 'Node 2'},
]);
var edges = new vis.DataSet([
  {from: 1, to: 2}
]);
var container = document.getElementById('mynetwork');
var data = {nodes: nodes, edges: edges};
var options = {};
var network = new vis.Network(container, data, options);

3d-force-graph:

const Graph = ForceGraph3D()
  (document.getElementById('3d-graph'))
    .graphData({
      nodes: [{id: 'Node 1'}, {id: 'Node 2'}],
      links: [{source: 'Node 1', target: 'Node 2'}]
    });

Graph theory (network) library for visualisation and analysis

Pros of Cytoscape.js

  • More extensive and mature library with a wider range of graph theory algorithms and analysis tools
  • Supports both 2D and 3D rendering, offering more flexibility in visualization options
  • Larger community and ecosystem, with more plugins and extensions available

Cons of Cytoscape.js

  • Steeper learning curve due to its more comprehensive feature set
  • Potentially slower performance for large graphs compared to 3d-force-graph's WebGL-based rendering

Code Comparison

3d-force-graph:

const Graph = ForceGraph3D()
  (document.getElementById('3d-graph'))
    .graphData(myData)
    .nodeLabel('id')
    .nodeAutoColorBy('group');

Cytoscape.js:

var cy = cytoscape({
  container: document.getElementById('cy'),
  elements: myData,
  style: [ /* ... */ ],
  layout: { name: 'cose' }
});

Both libraries offer concise ways to create and customize graph visualizations, but Cytoscape.js requires more configuration for styling and layout. 3d-force-graph provides a more streamlined API for quick 3D force-directed graph creation, while Cytoscape.js offers greater control and extensibility for complex graph applications.

16,856

Open-source JavaScript charting library behind Plotly and Dash

Pros of plotly.js

  • More comprehensive data visualization library with a wide range of chart types
  • Extensive documentation and community support
  • Built-in interactivity and responsiveness

Cons of plotly.js

  • Larger file size and potentially slower performance for complex visualizations
  • Steeper learning curve due to its extensive feature set
  • Less specialized for force-directed graph visualizations

Code Comparison

plotly.js:

var trace = {
  x: [1, 2, 3, 4],
  y: [10, 15, 13, 17],
  type: 'scatter'
};

var data = [trace];
Plotly.newPlot('myDiv', data);

3d-force-graph:

const Graph = ForceGraph3D()
  .graphData({
    nodes: [{id: 'a'}, {id: 'b'}, {id: 'c'}],
    links: [{source: 'a', target: 'b'}, {source: 'b', target: 'c'}]
  })
  .nodeLabel('id')
  .onNodeClick(node => window.open(`https://example.com/${node.id}`, '_blank'));

While plotly.js offers a broader range of visualization options and more extensive documentation, 3d-force-graph provides a more specialized and lightweight solution for force-directed graph visualizations in 3D. The code comparison illustrates the difference in complexity and focus between the two libraries.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

3D Force-Directed Graph

NPM package Build Size NPM Downloads

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 ngraph for the underlying physics engine.

See also the 2D canvas version, VR version and AR version.

And check out the React bindings.

Examples

Quick start

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

or using a script tag

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

then

const myGraph = ForceGraph3D();
myGraph(<myDOMElement>)
  .graphData(<myData>);

API reference

Initialisation

ForceGraph3d({ configOptions })(<domElement>)
Config optionsDescriptionDefault
controlType: strWhich type of control to use to control the camera. Choice between trackball, orbit or fly.trackball
rendererConfig: objectConfiguration parameters to pass to the ThreeJS WebGLRenderer constructor.{ antialias: true, alpha: true }
extraRenderers: arrayIf you wish to include custom objects that require a dedicated renderer besides WebGL, such as CSS3DRenderer, include in this array those extra renderer instances.[]

Data input

MethodDescriptionDefault
graphData([data])Getter/setter for graph data structure (see below for syntax details). Can also be used to apply incremental updates.{ nodes: [], links: [] }
jsonUrl([url])URL of JSON file to load graph data directly from, as an alternative to specifying graphData directly.
nodeId([str])Node object accessor attribute for unique node id (used in link objects source/target).id
linkSource([str])Link object accessor attribute referring to id of source node.source
linkTarget([str])Link object accessor attribute referring to id of target node.target

Container layout

MethodDescriptionDefault
width([px])Getter/setter for the canvas width.<window width>
height([px])Getter/setter for the canvas height.<window height>
backgroundColor([str])Getter/setter for the chart background color.#000011
showNavInfo([boolean])Getter/setter for whether to show the navigation controls footer info.true

Node styling

MethodDescriptionDefault
nodeRelSize([num])Getter/setter for the ratio of node sphere volume (cubic px) per value unit.4
nodeVal([num, str or fn])Node object accessor function, attribute or a numeric constant for the node numeric value (affects sphere volume).val
nodeLabel([str or fn])Node object accessor function or attribute for name (shown in label). Supports plain text or HTML content. Note that this method uses innerHTML internally, so make sure to pre-sanitize any user-input content to prevent XSS vulnerabilities.name
nodeVisibility([boolean, str or fn])Node object accessor function, attribute or a boolean constant for whether to display the node.true
nodeColor([str or fn])Node object accessor function or attribute for node color (affects sphere color).color
nodeAutoColorBy([str or fn])Node object accessor function (fn(node)) or attribute (e.g. 'type') to automatically group colors by. Only affects nodes without a color attribute.
nodeOpacity([num])Getter/setter for the nodes sphere opacity, between [0,1].0.75
nodeResolution([num])Getter/setter for the geometric resolution of each node, expressed in how many slice segments to divide the circumference. Higher values yield smoother spheres.8
nodeThreeObject([Object3d, str or fn])Node object accessor function or attribute for generating a custom 3d object to render as graph nodes. Should return an instance of ThreeJS Object3d. If a falsy value is returned, the default 3d object type will be used instead for that node.default node object is a sphere, sized according to val and styled according to color.
nodeThreeObjectExtend([bool, str or fn])Node object accessor function, attribute or a boolean value for whether to replace the default node when using a custom nodeThreeObject (false) or to extend it (true).false

Link styling

MethodDescriptionDefault
linkLabel([str or fn])Link object accessor function or attribute for name (shown in label). Supports plain text or HTML content. Note that this method uses innerHTML internally, so make sure to pre-sanitize any user-input content to prevent XSS vulnerabilities.name
linkVisibility([boolean, str or fn])Link object accessor function, attribute or a boolean constant for whether to display the link line. A value of false maintains the link force without rendering it.true
linkColor([str or fn])Link object accessor function or attribute for line color.color
linkAutoColorBy([str or fn])Link object accessor function (fn(link)) or attribute (e.g. 'type') to automatically group colors by. Only affects links without a color attribute.
linkOpacity([num])Getter/setter for line opacity of links, between [0,1].0.2
linkWidth([num, str or fn])Link object accessor function, attribute or a numeric constant for the link line width. A value of zero will render a ThreeJS Line whose width is constant (1px) regardless of distance. Values are rounded to the nearest decimal for indexing purposes.0
linkResolution([num])Getter/setter for the geometric resolution of each link, expressed in how many radial segments to divide the cylinder. Higher values yield smoother cylinders. Applicable only to links with positive width.6
linkCurvature([num, str or fn])Link object accessor function, attribute or a numeric constant for the curvature radius of the link line. Curved lines are represented as 3D bezier curves, and any numeric value is accepted. A value of 0 renders a straight line. 1 indicates a radius equal to half of the line length, causing the curve to approximate a semi-circle. For self-referencing links (source equal to target) the curve is represented as a loop around the node, with length proportional to the curvature value. Lines are curved clockwise for positive values, and counter-clockwise for negative values. Note that rendering curved lines is purely a visual effect and does not affect the behavior of the underlying forces.0
linkCurveRotation([num, str or fn])Link object accessor function, attribute or a numeric constant for the rotation along the line axis to apply to the curve. Has no effect on straight lines. At 0 rotation, the curve is oriented in the direction of the intersection with the XY plane. The rotation angle (in radians) will rotate the curved line clockwise around the "start-to-end" axis from this reference orientation.0
linkMaterial([Material, str or fn])Link object accessor function or attribute for specifying a custom material to style the graph links with. Should return an instance of ThreeJS Material. If a falsy value is returned, the default material will be used instead for that link.default link material is MeshLambertMaterial styled according to color and opacity.
linkThreeObject([Object3d, str or fn])Link object accessor function or attribute for generating a custom 3d object to render as graph links. Should return an instance of ThreeJS Object3d. If a falsy value is returned, the default 3d object type will be used instead for that link.default link object is a line or cylinder, sized according to width and styled according to material.
linkThreeObjectExtend([bool, str or fn])Link object accessor function, attribute or a boolean value for whether to replace the default link when using a custom linkThreeObject (false) or to extend it (true).false
linkPositionUpdate([fn(linkObject, { start, end }, link)])Getter/setter for the custom function to call for updating the position of links at every render iteration. It receives the respective link ThreeJS Object3d, the start and end coordinates of the link ({x,y,z} each), and the link's data. If the function returns a truthy value, the regular position update function will not run for that link.
linkDirectionalArrowLength([num, str or fn])Link object accessor function, attribute or a numeric constant for the length of the arrow head indicating the link directionality. The arrow is displayed directly over the link line, and points in the direction of source > target. A value of 0 hides the arrow.0
linkDirectionalArrowColor([str or fn])Link object accessor function or attribute for the color of the arrow head.color
linkDirectionalArrowRelPos([num, str or fn])Link object accessor function, attribute or a numeric constant for the longitudinal position of the arrow head along the link line, expressed as a ratio between 0 and 1, where 0 indicates immediately next to the source node, 1 next to the target node, and 0.5 right in the middle.0.5
linkDirectionalArrowResolution([num])Getter/setter for the geometric resolution of the arrow head, expressed in how many slice segments to divide the cone base circumference. Higher values yield smoother arrows.8
linkDirectionalParticles([num, str or fn])Link object accessor function, attribute or a numeric constant for the number of particles (small spheres) to display over the link line. The particles are distributed equi-spaced along the line, travel in the direction source > target, and can be used to indicate link directionality.0
linkDirectionalParticleSpeed([num, str or fn])Link object accessor function, attribute or a numeric constant for the directional particles speed, expressed as the ratio of the link length to travel per frame. Values above 0.5 are discouraged.0.01
linkDirectionalParticleWidth([num, str or fn])Link object accessor function, attribute or a numeric constant for the directional particles width. Values are rounded to the nearest decimal for indexing purposes.0.5
linkDirectionalParticleColor([str or fn])Link object accessor function or attribute for the directional particles color.color
linkDirectionalParticleResolution([num])Getter/setter for the geometric resolution of each directional particle, expressed in how many slice segments to divide the circumference. Higher values yield smoother particles.4
emitParticle(link)An alternative mechanism for generating particles, this method emits a non-cyclical single particle within a specific link. The emitted particle shares the styling (speed, width, color) of the regular particle props. A valid link object that is included in graphData should be passed as a single parameter.

Render control

MethodDescriptionDefault
pauseAnimation()Pauses the rendering cycle of the component, effectively freezing the current view and cancelling all user interaction. This method can be used to save performance in circumstances when a static image is sufficient.
resumeAnimation()Resumes the rendering cycle of the component, and re-enables the user interaction. This method can be used together with pauseAnimation for performance optimization purposes.
cameraPosition([{x,y,z}], [lookAt], [ms])Getter/setter for the camera position, in terms of x, y, z coordinates. Each of the coordinates is optional, allowing for motion in just some dimensions. The optional second argument can be used to define the direction that the camera should aim at, in terms of an {x,y,z} point in the 3D space. The 3rd optional argument defines the duration of the transition (in ms) to animate the camera motion. A value of 0 (default) moves the camera immediately to the final position.By default the camera will face the center of the graph at a z distance proportional to the amount of nodes in the system.
zoomToFit([ms], [px], [nodeFilterFn])Automatically moves the camera so that all of the nodes become visible within its field of view, aiming at the graph center (0,0,0). If no nodes are found no action is taken. It accepts three optional arguments: the first defines the duration of the transition (in ms) to animate the camera motion (default: 0ms). The second argument is the amount of padding (in px) between the edge of the canvas and the outermost node location (default: 10px). The third argument specifies a custom node filter: node => <boolean>, which should return a truthy value if the node is to be included. This can be useful for focusing on a portion of the graph.(0, 10, node => true)
postProcessingComposer()Access the post-processing composer. Use this to add post-processing rendering effects to the scene. By default the composer has a single pass (RenderPass) that directly renders the scene without any effects.
lights([array])Getter/setter for the list of lights to use in the scene. Each item should be an instance of Light.AmbientLight + DirectionalLight (from above)
scene()Access the internal ThreeJS Scene. Can be used to extend the current scene with additional objects not related to 3d-force-graph.
camera()Access the internal ThreeJS Camera.
renderer()Access the internal ThreeJS WebGL renderer.
controls()Access the internal ThreeJS controls object.
refresh()Redraws all the nodes/links.

Force engine configuration

MethodDescriptionDefault
forceEngine([str])Getter/setter for which force-simulation engine to use (d3 or ngraph).d3
numDimensions([int])Getter/setter for number of dimensions to run the force simulation on (1, 2 or 3).3
dagMode([str])Apply layout constraints based on the graph directionality. Only works correctly for DAG graph structures (without cycles). Choice between td (top-down), bu (bottom-up), lr (left-to-right), rl (right-to-left), zout (near-to-far), zin (far-to-near), radialout (outwards-radially) or radialin (inwards-radially).
dagLevelDistance([num])If dagMode is engaged, this specifies the distance between the different graph depths.auto-derived from the number of nodes
dagNodeFilter([fn])Node accessor function to specify nodes to ignore during the DAG layout processing. This accessor method receives a node object and should return a boolean value indicating whether the node is to be included. Excluded nodes will be left unconstrained and free to move in any direction.node => true
onDagError([fn])Callback to invoke if a cycle is encountered while processing the data structure for a DAG layout. The loop segment of the graph is included for information, as an array of node ids. By default an exception will be thrown whenever a loop is encountered. You can override this method to handle this case externally and allow the graph to continue the DAG processing. Strict graph directionality is not guaranteed if a loop is encountered and the result is a best effort to establish a hierarchy.throws exception
d3AlphaMin([num])Getter/setter for the simulation alpha min parameter, only applicable if using the d3 simulation engine.0
d3AlphaDecay([num])Getter/setter for the simulation intensity decay parameter, only applicable if using the d3 simulation engine.0.0228
d3VelocityDecay([num])Getter/setter for the nodes' velocity decay that simulates the medium resistance, only applicable if using the d3 simulation engine.0.4
d3Force(str, [fn])Getter/setter for the internal forces that control the d3 simulation engine. Follows the same interface as d3-force-3d's simulation.force. Three forces are included by default: 'link' (based on forceLink), 'charge' (based on forceManyBody) and 'center' (based on forceCenter). Each of these forces can be reconfigured, or new forces can be added to the system. This method is only applicable if using the d3 simulation engine.
d3ReheatSimulation()Reheats the force simulation engine, by setting the alpha value to 1. Only applicable if using the d3 simulation engine.
ngraphPhysics([object])Specify custom physics configuration for ngraph, according to its configuration object syntax. This method is only applicable if using the ngraph simulation engine.ngraph default
warmupTicks([int])Getter/setter for number of layout engine cycles to dry-run at ignition before starting to render.0
cooldownTicks([int])Getter/setter for how many build-in frames to render before stopping and freezing the layout engine.Infinity
cooldownTime([num])Getter/setter for how long (ms) to render for before stopping and freezing the layout engine.15000
onEngineTick(fn)Callback function invoked at every tick of the simulation engine.-
onEngineStop(fn)Callback function invoked when the simulation engine stops and the layout is frozen.-

Interaction

MethodDescriptionDefault
onNodeClick(fn)Callback function for node (left-button) clicks. The node object and the event object are included as arguments onNodeClick(node, event).-
onNodeRightClick(fn)Callback function for node right-clicks. The node object and the event object are included as arguments onNodeRightClick(node, event).-
onNodeHover(fn)Callback function for node mouse over events. The node object (or null if there's no node under the mouse line of sight) is included as the first argument, and the previous node object (or null) as second argument: onNodeHover(node, prevNode).-
onNodeDrag(fn)Callback function for node drag interactions. This function is invoked repeatedly while dragging a node, every time its position is updated. The node object is included as the first argument, and the change in coordinates since the last iteration of this function are included as the second argument in format {x,y,z}: onNodeDrag(node, translate).-
onNodeDragEnd(fn)Callback function for the end of node drag interactions. This function is invoked when the node is released. The node object is included as the first argument, and the entire change in coordinates from initial location are included as the second argument in format {x,y,z}: onNodeDragEnd(node, translate).-
onLinkClick(fn)Callback function for link (left-button) clicks. The link object and the event object are included as arguments onLinkClick(link, event).-
onLinkRightClick(fn)Callback function for link right-clicks. The link object and the event object are included as arguments onLinkRightClick(link, event).-
onLinkHover(fn)Callback function for link mouse over events. The link object (or null if there's no link under the mouse line of sight) is included as the first argument, and the previous link object (or null) as second argument: onLinkHover(link, prevLink).-
onBackgroundClick(fn)Callback function for click events on the empty space between the nodes and links. The event object is included as single argument onBackgroundClick(event).-
onBackgroundRightClick(fn)Callback function for right-click events on the empty space between the nodes and links. The event object is included as single argument onBackgroundRightClick(event).-
linkHoverPrecision([int])Whether to display the link label when gazing the link closely (low value) or from far away (high value).1
enablePointerInteraction([boolean])Getter/setter for whether to enable the mouse tracking events. This activates an internal tracker of the canvas mouse position and enables the functionality of object hover/click and tooltip labels, at the cost of performance. If you're looking for maximum gain in your graph performance it's recommended to switch off this property.true
enableNodeDrag([boolean])Getter/setter for whether to enable the user interaction to drag nodes by click-dragging. Only supported on the d3 force engine. If enabled, every time a node is dragged the simulation is re-heated so the other nodes react to the changes. Only applicable if enablePointerInteraction is true and using the d3 force engine.true
enableNavigationControls([boolean])Getter/setter for whether to enable the trackball navigation controls used to move the camera using mouse interactions (rotate/zoom/pan).true

Utility

MethodDescription
getGraphBbox([nodeFilterFn])Returns the current bounding box of the nodes in the graph, formatted as { x: [<num>, <num>], y: [<num>, <num>], z: [<num>, <num>] }. If no nodes are found, returns null. Accepts an optional argument to define a custom node filter: node => <boolean>, which should return a truthy value if the node is to be included. This can be useful to calculate the bounding box of a portion of the graph.
graph2ScreenCoords(x, y, z)Utility method to translate node coordinates to the viewport domain. Given a set of x,y,z graph coordinates, returns the current equivalent {x, y} in viewport coordinates.
screen2GraphCoords(x, y, distance)Utility method to translate viewport distance coordinates to the graph domain. Given a pair of x,y screen coordinates and distance from the camera, returns the current equivalent {x, y, z} in the domain of graph node coordinates.

Input JSON syntax

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

Giving Back

paypal If this project has helped you and you'd like to contribute back, you can always buy me a ☕!

NPM DownloadsLast 30 Days