Hysen Labs
Open-source project
xyflow/xyflow avatar
xyflow

xyflow

React Flow | Svelte Flow - Powerful open source libraries for building node-based UIs with React (https://reactflow.dev) or Svelte (https://svelteflow.dev). Ready out-of-the-box and infinitely customizable.

38,026 stars2,505 forksTypeScriptMIT
01
DEEP OPEN-SOURCE ANALYSIS

Xyflow: React Flow and Svelte Flow under one roof

A monorepo that houses React Flow and Svelte Flow, two open source libraries for building node based user interfaces, plus the helper package they share.

02
DEEP OPEN-SOURCE ANALYSIS

Four packages, one repository

The xyflow repository is home to four packages. React Flow 12 ships as @xyflow/react in packages/react, while React Flow 11 lives on the v11 branch under the reactflow name. Svelte Flow is @xyflow/svelte in packages/svelte, and a shared helper library, @xyflow/system, lives in packages/system. The libraries are described as ready out of the box and infinitely customizable, targeting React and Svelte respectively. Keeping both under one repository means fixes and features can move between them through the shared system package. The main sites are reactflow.dev and svelteflow.dev.

03
DEEP OPEN-SOURCE ANALYSIS

How it stays open source

The README spells out the funding model. Personal projects need no sponsorship; support comes through bug reports, screenshots, and stars. Organizations that make money using the libraries are asked to support development through React Flow Pro for React Flow, or GitHub Sponsors for both libraries. The goal is to keep the libraries developed and maintained under an MIT license.

04
DEEP OPEN-SOURCE ANALYSIS

Releases and getting started

The recommended starting point is the React Flow or Svelte Flow learn section. Releases run through changesets combined with the changeset GitHub action: pull requests carry a changeset where relevant, merge into main, and a changeset PR bumps all packages before a final release to GitHub and npm. The xyflow team maintains both libraries, reachable through a contact form or Discord.

05
DEEP OPEN-SOURCE ANALYSIS

Editorial conclusion

A small monorepo with a clear structure: two UI libraries, one shared helper, and an explicit sponsorship ask. The README is honest about how the project stays free.

06
DEEP OPEN-SOURCE ANALYSIS

Official sources

07
Community notes

Community notes