Hi. :wave: By running in react [`strict-mode`](https://reactjs.org/docs/strict-mode.html), I noticed that that `react-vis` relies on the now deprecated [`componentWillReciveProps`](https://reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops). With a quick search in the repo I found the following usages (examples are omitted): - [`ArcSeries`](https://github.com/uber/react-vis/blob/35c8950722e9ad60214399291eda731ac31af267/src/plot/series/arc-series.js#L78) - [`ThreeMap`](https://github.com/uber/react-vis/blob/35c8950722e9ad60214399291eda731ac31af267/src/treemap/index.js#L103) - [`makeFlexible`](https://github.com/uber/react-vis/blob/7a67a4a1d7856a9fc09a28c1f3738ef064f53ffd/src/make-vis-flexible.js#L143) - [`XyPlot`](https://github.com/uber/react-vis/blob/7a67a4a1d7856a9fc09a28c1f3738ef064f53ffd/src/plot/xy-plot.js#L145) These should be easily resolvable by moving to either `getDerivedStateFromProps` or `componentDidUpdate` or memoization as detailed [here](https://reactjs.org/docs/react-component.html#unsafe_componentwillreceiveprops) and [here](https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html). Are there any plans for doing or concerns about doing these changes? If these changes makes sense for the project, I could make a PR for them 👍