3d-force-graph

v1.74.5

UI component for a 3D force-directed graph using ThreeJS and d3-force-3d layout engine For more information about how to use this package see README

Latest version published 3 days ago

License: MIT

NPM

GitHub

Package Health Score

76 / 100

security
No known security issues
popularity
Popular
maintenance
Sustainable
community
Sustainable

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version			Vulnerabilities	License Risk
1.74.5	\|	12/2024	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.73.6	\|	11/2024	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.73.3	\|	03/2024	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.23.0	\|	02/2018	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.5.3	\|	04/2017	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Popular

Weekly Downloads (18,910)

GitHub Stars: 4.88K
Forks: 841
Contributors: 20

Direct Usage Popularity

The npm package 3d-force-graph receives a total of 18,910 downloads a week. As such, we scored 3d-force-graph popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package 3d-force-graph, we found that it has been starred 4,879 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 20
Funding: No

With more than 10 contributors for the 3d-force-graph repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like 3d-force-graph is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 235
Open PR: 4
Last Release: 3 days ago
Last Commit: 3 days ago

Further analysis of the maintenance status of 3d-force-graph based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that 3d-force-graph demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=12

Age: 8 years
Dependencies: 5 Direct
Versions: 327
Install Size: 10.1 MB
Dist-tags: 1
# of Files: 55
Maintainers: 1
TS Typings: Yes

3d-force-graph has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use 3d-force-graph?

To help you get started, we've collected the most common ways that 3d-force-graph is being used within popular public projects.

artyomtrityak / d3-explorer / static / javascript / components / 3d-charts / force-3d-camera.js View on Github

componentDidMount() {
    this.graph = ForceGraph3D()(this.chartRef)
      .width(this.chartRef.clientWidth - 100)
      .height(window.innerHeight - 200)
      .forceEngine("ngraph")
      .backgroundColor("#FFFFFF")
      .nodeAutoColorBy("group")
      .graphData(this.state.data);

    this.startOrbit();
  }

View more ways to use 3d-force-graph

3D Force-Directed Graph

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

Basic (source)
Asynchronous load (source)
Larger graph (~4k elements) (source)
Directional arrows (source)
Directional moving particles (source)
Curved lines and self links (source)
Auto-colored nodes/links (source)
Text as nodes (source)
Images as nodes (source)
HTML in nodes (source)
Custom node geometries (source)
Gradient Links (source)
Text in Links (source)
Orbit controls (source)
Fly controls (source)
Camera automatic orbitting (source)
Click to focus on node (source)
Click to expand/collapse nodes (source)
Fix nodes after dragging (source)
Fit graph to canvas (source)
Highlight nodes/links (source)
Multiple Node Selection (source)
Dynamic data changes (source)
Node collision detection (source)
Manipulate link force distance (source)
Emit link particles on demand (source)
Force-directed tree (DAG mode) (source)
yarn.lock dependency graph (DAG mode) (source)
Add external objects to scene (source)
Bloom Post-Processing Effect (source)
Pause / Resume animation (source)

Quick start

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

or using a script tag

then

const myGraph = new ForceGraph3D()
  .graphData();

API reference

Initialisation

new ForceGraph3d(, { configOptions })

Config options	Description	Default
controlType: str	Which type of control to use to control the camera. Choice between trackball, orbit or fly.	`trackball`
rendererConfig: object	Configuration parameters to pass to the ThreeJS WebGLRenderer constructor.	`{ antialias: true, alpha: true }`
extraRenderers: array	If 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

Method	Description	Default
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

Method	Description	Default
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

Method	Description	Default
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

Method	Description	Default
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

Method	Description	Default
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 =>` , 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

Method	Description	Default
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

Method	Description	Default
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

Method	Description
getGraphBbox([nodeFilterFn])	Returns the current bounding box of the nodes in the graph, formatted as `{ x: [, ], y: [, ], z: [, ] }`. If no nodes are found, returns `null`. Accepts an optional argument to define a custom node filter: `node =>` , 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

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

3d-force-graph dependencies

accessor-fn kapsule three three-forcegraph three-render-objects

3d-force-graph development dependencies

@babel/core @babel/preset-env @rollup/plugin-babel @rollup/plugin-commonjs @rollup/plugin-node-resolve @rollup/plugin-terser postcss rimraf rollup rollup-plugin-dts rollup-plugin-postcss typescript

FAQs

What is 3d-force-graph?

UI component for a 3D force-directed graph using ThreeJS and d3-force-3d layout engine. Visit Snyk Advisor to see a full health score report for 3d-force-graph, including popularity, security, maintenance & community analysis.

Is 3d-force-graph popular?

The npm package 3d-force-graph receives a total of 18,910 weekly downloads. As such, 3d-force-graph popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is 3d-force-graph well maintained?

We found indications that 3d-force-graph maintenance is sustainable demonstrating some project activity. We saw a total of 20 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is 3d-force-graph safe to use?

The npm package 3d-force-graph was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 December-2024, at 01:34 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP