Hi, I’m Swizec Teller. Over the years I've helped over 10,000 engineers hone their craft. 

With React+D3v4 you'll learn the basics of building fast data visualization components in about an hour. Get started immediately without installing anything.

I based React+D3v4 on 20 years of experience with learning how to code on my own, reading blogs and articles, listening to professors, and working with mentors.

Don't know React? React+D3v4 starts at the very beginning.

Struggling with D3? Every function is explained.

Christina

I bought your course Because D3.js is highly flexible, and writing a bunch of method chaining sucks for D3

Frontend Engineer

Francois

I'm a react veteran who has always wanted to learn D3. I know enough about it to know there will be some quirks integrating with react, so figured your book would save me and my team from having to figure those out on our own. 

I use React because it is the sane way of doing things. I use D3 because I have to. I want nice interactive charts. I want to stay sane.

Software Engineer

Amit

In my old age, I love having practical examples to help me learn new things faster.

D3's docs alone are okay but marrying them with React (as a react newbie) is not as straightforward as someone handholding you through the process. And, since I don't have hours after work or on weekends to hack on things like I used to before I was married (or had kids), I need to optimize my learning.

I already owned your previous version and know it would be worth my money to buy the updated version.

Thanks for all of the hard work!

Freelance Engineer

Become a data visualization engineer with React + D3v4

We start with the presentation components because they're the least complicated. To render a collection of particles, we need:

- a stateless `Particle`
- a stateless `Particles`
- a proper `App`

None of them contain state, but `App` has to be a proper component so that we can use `componentDidMount`. We need it to attach D3 event listeners.

### Particle

The `Particle` component is a circle. It looks like this:

// src/components/Particles/Particle.jsx
import React from 'react';

const Particle = ({ x, y }) => (
	<circle cx={x} cy={y} r="1.8" />
);

export default Particle;


It takes `x` and `y` coordinates and returns an SVG circle.

### Particles

The `Particles` component isn't much smarter – it returns a list of circles wrapped in a grouping element, like this:

// src/components/Particles/index.jsx
import React from 'react';
import Particle from './Particle';

const Particles = ({ particles }) => (
	<g>{particles.map(particle =>
		<Particle key={particle.id}
		          {...particle} />
		)}
	</g>
);

export default Particles;


Walk through the array of particles, render a Particle component for each. Declarative rendering that you've seen before :)

We can take an array of `{id, x, y}` objects and render SVG circles. Now comes our first fun component: the `App`.

### App

`App` takes care of rendering the scene and attaching d3 event listeners. It's not _really_ a presentation component because it gets actions via props and ties them to mouse events. This is a Redux faux pas, but it works well in practice.

The rendering part looks like this:

We start with the presentation components because they're the least complicated. To render a collection of particles, we need:

- a stateless `Particle`
- a stateless `Particles`
- a proper `App`

None of them contain state, but `App` has to be a proper component so that we can use `componentDidMount`. We need it to attach D3 event listeners.

# Particle

The `Particle` component is a circle. It looks like this:


It takes `x` and `y` coordinates and returns an SVG circle.

# Particles

The `Particles` component isn't much smarter – it returns a list of circles wrapped in a grouping element, like this:


Walk through the array of particles, render a Particle component for each. Declarative rendering that you've seen before :)

We can take an array of `{id, x, y}` objects and render SVG circles. Now comes our first fun component: the `App`.

# App

`App` takes care of rendering the scene and attaching d3 event listeners. It's not _really_ a presentation component because it gets actions via props and ties them to mouse events. This is a Redux faux pas, but it works well in practice.

The rendering part looks like this:

Introduction

The Meat Start

Simpler Environment

The New Meat

Animation

Animating React Redux

Speed Optimizations

Conclusion

Appendices

3 presentation components

Particle

Particles