visx

Motivation

Goal

The goal is to create a library of components you can use to make both your own reusable chart library or your slick custom one-off chart. visx is largely unopinionated and is meant to be built upon. Keep your bundle sizes down and use only the packages you need.

How?

Under the hood, visx is using d3 for the calculations and math. If you're creating your own awesome chart library on top of visx, it's easy to create a component API that hides d3 entirely. Meaning your team could create charts as easily as using reusable React components.

But why?

Mixing two mental models for updating the DOM is never a good time. Copy and pasting d3 code into componentDidMount() is just that. This collection of components lets you easily build your own reusable visualization charts or library without having to learn d3. No more selections or enter()/exit()/update().

FAQ

1. What does visx stand for?

   visx stands for visualization components.

2. Do you plan on supporting animation/transitions?

   A common criticism of visx is it doesn't have animation baked in, but this was a conscious choice. It's a powerful feature to not bake it in.

   Imagine your app already bundles react-motion, adding a hypothetical @visx/animation is bloat. Since visx is react, it already supports all react animation libs.

   Charting libraries are like style guides. Each org or app will eventually want full control over their own implementation.

   visx makes this easier for everyone. No need to reinvent the wheel each time.

   more info: https://github.com/airbnb/visx/issues/6

   examples:

   • Collapsible tree with react-move by @techniq (Demo) (Radial demo)
   • Animation with react-spring by @drcmda (Demo)

3. Do I have to use every package to make a chart?

   nope! pick and choose the packages you need.

4. Can I use this to create my own library of charts for my team?

   Please do.

5. Does visx work with preact?

   yup! need to alias react + react-dom and use preact-compat.

6. I like using d3.

   Me too.