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

cytoscape-dom-node

v2.1.0

Published

Cytoscape extension for making nodes into DOM elements

Readme

cytoscape-dom-node

This extension lets you set DOM elements as nodes. When enabled providing the DOM element by setting the dom node data will cause the DOM element to be rendered on top of the node, and the node will be set to the size of the DOM element.

For a full working demo, see codepen abWdVOG. There are also more demos in ./demos.

History

v2.1.0 has bug fixes / improvements outstanding since v1. v2.0.0 - v2.0.1 is a typescript conversion, and SHOULD be backwards compatible with v1. v1.3.0 is the latest pre typescript incarnation.

Dependencies

  • cytoscape ^3.19.0

Extension registration

Import cytoscape-dom-node, and register it as an extension with Cytoscape:

import cytoscape from "cytoscape";
import cytoscapeDomNode from "cytoscape-dom-node";

cytoscape.use(cytoscapeDomNode);

CommonJS is still supported:

const cytoscape = require("cytoscape");
const cytoscapeDomNode = require("cytoscape-dom-node");

cytoscape.use(cytoscapeDomNode);

Or it can be included via a <script> tag after cytoscape, and will register itself:

<script type="text/javascript" charset="utf8" src="path/to/cytoscape.js"></script>
<script
  type="text/javascript"
  charset="utf8"
  src="path/to/cytoscape-dom-node.global.js"
></script>

Usage instructions

Create a cytoscape instance and call domNode on it:

const cy = cytoscape({
  container: document.getElementById("id-of-my-cytoscape-container"),
  elements: [],
});

const domNodeRenderer = cy.domNode();

Now add a node with dom in the data, set to a DOM element:

const div = document.createElement("div");
div.innerHTML = `node ${id}`;

cy.add({
  data: {
    dom: div,
    id,
  },
});

The div you created will be shown as the node now.

You can retrieve the DOM element for a Cytoscape node id:

const nodeElement = domNodeRenderer.nodeDom(id);

The previous node_dom(id) method is kept as a backwards compatible alias.

When a Cytoscape node is removed, cytoscape-dom-node removes the DOM element it appended for that node. Nodes using skipNodeAppend remain caller-owned and are not removed from the DOM.

See codepen abWdVOG for a working example.

Skip Node Append

The skipNodeAppend node data option controls whether cytoscape-dom-node appends the provided DOM node to the configured DOM container. By default, cytoscape-dom-node appends the node to the container.

In certain scenarios, such as when using EmberJS or another front-end framework, you might have already rendered the nodes to the DOM. In these cases, set skipNodeAppend to true to keep control over rendering.

const div = document.querySelector("#alreadyRenderedNodeId");
cy.add({
  data: {
    dom: div,
    id,
    skipNodeAppend: true,
  },
});

The legacy skip_node_append name remains supported.

Options

domContainer allows a container element to be specified. It will be used for nodes instead of the element cytoscape-dom-node would otherwise create. It is the caller's responsibility to style the given element appropriately:

cy.domNode({ domContainer: someElement });

The legacy dom_container name remains supported.

interactiveSelector sets which child elements should receive native DOM interaction instead of becoming Cytoscape gestures. Matching controls get pointer-events: auto, and pointerdown, mousedown, and touchstart are stopped during capture so inputs and buttons do not start graph drags. It defaults to common controls:

cy.domNode({
  interactiveSelector:
    "input, button, select, textarea, a[href], [contenteditable]:not([contenteditable='false']), [data-cy-dom-node-interactive]",
});

For draggable DOM-backed nodes, make the node shell pass pointer events through to Cytoscape and let the renderer re-enable matching controls:

.dom-node {
  pointer-events: none;
}

Set interactiveSelector to false to disable this control isolation.

Interaction State

DOM nodes mirror Cytoscape selection state with the selected class. Selected or grabbed nodes receive z-index 11; other DOM nodes receive z-index 10.

Development

This package is authored in TypeScript and emits CommonJS, ESM, browser global, and declaration outputs into dist.

Useful commands:

npm run lint
npm run typecheck
npm run test
npm run test:coverage
npm run build
npm run docs
npm run check