design-infravis-network · Styled network nodes vs similar
1 option side by side. Our @design-infra pieces render live under the design system you choose; upstream pieces show their live demo where the host allows embedding, otherwise a screenshot with a link to the real thing. Pick or pass, then copy the feedback for your agent.
- No preview yetOpen live demo ↗recipeTechnicalRefined
Integration recipe: the command installs the library, not a standalone finished component. Adapt the linked upstream API/example to your data and brand. Dual Apache-2.0/MIT licensing; preserve notices for the option you use. Prefer the documented standalone import or satisfy the peer build dependencies, including vis-data. Bound the physics simulation, provide a sized parent and destroy Network/listeners on unmount. A graph editor still needs application-level validation, storage and permissions. Upstream: https://github.com/visjs/vis-network. License: (Apache-2.0 OR MIT). Package metadata: vis-network@10.1.2; peers: uuid ^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0 || ^11.0.0 || ^13.0.0 || ^14.0.0; keycharm ^0.2.0 || ^0.3.0 || ^0.4.0; vis-data >=8.0.0; vis-util >=6.0.0; @egjs/hammerjs ^2.0.0; component-emitter ^1.3.0 || ^2.0.0. Runtime integration is not verified by this metadata sync.
$pnpm add vis-network vis-data
Feedback for your agent
Pick or pass on each option (add a reason if you like), then paste this back into your agent's chat.
From design-infra compare — vis-network · Styled network nodes vs similar: (no picks yet) Compare: https://www.owencoonahan.xyz/design-infra/compare?ids=vis-network/node-styles&label=vis-network+%C2%B7+Styled+network+nodes+vs+similar