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

@headflow/react

v0.2.0

Published

React adapter for HeadFlow — headless node-graph UI

Readme

@headflow/react

React bindings for HeadFlow — a headless node-graph engine. This package wraps @headflow/core with hooks and a small provider so you can build flow UIs with refs and re-renders, without the engine dictating DOM structure or CSS.

Requirements: React 18+, react-dom 18+.


What you get

  • useFlowCanvas — Canvas ref + FlowProvider to scope one flow instance.
  • useNode / useHandle — Attach draggable nodes and source/target handles by ref.
  • useEdges — Reactive edge list with screen-space endpoints for your SVG/canvas layer.
  • useSelection / useLasso — Selection state and lasso overlay helpers.
  • useFlowContext — Access the underlying FlowEngine when you need imperative APIs.

Types such as Edge, Point, SerializedGraph, and FlowEngine are re-exported from @headflow/core for convenience.


Install

npm install @headflow/react @headflow/core

Peers: react, react-dom (>=18).


Minimal example

import { useFlowCanvas, useNode, useHandle, useEdges } from '@headflow/react'

export function App() {
  const { canvasRef, FlowProvider } = useFlowCanvas()

  return (
    <FlowProvider>
      <div
        ref={canvasRef}
        style={{ position: 'relative', width: '100%', height: '100%' }}
      >
        <MyNode id="n1" defaultPosition={{ x: 60, y: 100 }} />
        <MyNode id="n2" defaultPosition={{ x: 300, y: 100 }} />
        <EdgeLayer />
      </div>
    </FlowProvider>
  )
}

function MyNode({ id, defaultPosition }: { id: string; defaultPosition: { x: number; y: number } }) {
  const nodeRef = useNode(id, { defaultPosition })
  const outRef = useHandle(id, 'out', 'source')
  const inRef = useHandle(id, 'in', 'target')

  return (
    <div ref={nodeRef} style={{ position: 'absolute' }}>
      <div ref={inRef} />
      My node
      <div ref={outRef} />
    </div>
  )
}

function EdgeLayer() {
  const edges = useEdges()
  return (
    <svg style={{ position: 'absolute', inset: 0, pointerEvents: 'none' }}>
      {edges.map((e) => (
        <line
          key={e.id}
          x1={e.source.pt.x}
          y1={e.source.pt.y}
          x2={e.target.pt.x}
          y2={e.target.pt.y}
          stroke="#888"
        />
      ))}
    </svg>
  )
}

Render your own nodes (cards, ports, icons); HeadFlow only needs refs and the attribute contract documented in @headflow/core.


Documentation


See also

| Package | Use case | |---------|----------| | @headflow/core | Vanilla / custom framework integration | | @headflow/solid | SolidJS apps | | @headflow/renderer | Bezier paths & lasso math for SVG |

License

MIT