1 November 2022
What’s new at React Flow - Fall 2022 🍂
Howdy! Here’s a dispatch straight from our desks about what’s happened in the last couple of months at React Flow: updates, news, and a peek behind-the-scenes. Here we go.
Launching v11 and post-release housekeeping
React Flow v11 went live in early October (woohoo! whole blog post all about it if you haven’t seen yet.
), and Moritz wrote aPost-launch, we took a few weeks to tend to our current structures. We made some fixes to accessibility updates from v11 (thanks to some wonderful user feedback nodesFocusable
and edgesFocusable
to make the keyboard handling better configurable , and took some time to refocus ourselves for the end of the year. (Shout-out to Supabase for the inspiration on post-release weeks.)
Slowly but surely, folks are starting to use our new package name. react-flow-renderer
is dead, long live reactflow
! (data from npmtrends)
Examples, examples, examples
We’ve added a bunch of new examples to the docs including:
- Collision Detection
- Easy Connect
- Download Image
- Tailwind Implementation
- Turborepo style
- Light / Dark Mode
- Workflow Builder (aka the “taco flow” for Pro subscribers)
Our first round of user research
With the indispensable help of Eileen, we talked to some React Flow Pro subscribers and asked them about what they expect and need from us. It was great to talk to people using React Flow on a daily basis in ways we didn’t imagine before. We’ll be doing ongoing user research with people like yourself! If you’re up for helping us with that, keep your eyes on our Discord, Twitter, or sign up for our Newsletter:
We’ll be sharing out some of those findings from our research at our lightning talk at React Day Berlin in December - if you’re coming, let us know so we can say hi 👋🏻
Explaining ourselves better
We also added some basic explainers to the docs (answering questions like “what is a handle?”) to encourage easier onboarding for folks who are new to React Flow.
We also changed our docs to make it clear that anyone is allowed to remove the attribution (even without a subscription). React Flow is under an MIT License, so you can do anything you want with the code.
In the office
Over at our office in Kreuzberg, Berlin, we put up a whiteboard, ordered some embroidered hats, had a 4-legged visitor, and continue to be entertained by the ongoing construction site across the street.
What’s next?
As we move into the winter, we’re thinking about how we want to wrap up this year, and what 2023 will bring. Some of the big questions we’re asking ourselves these days are:
- How might we help devs to improve the UX of their flows? (maybe themes, guides about styling, or sharing more custom styles?)
- Giving more opportunity for feedback and discussion with the React Flow community
- Show and tell more openly about what we do and how we do it at React Flow
And finally, Moritz made this handy custom node.
Happy coding and see you around!
John
28 September 2022
React Flow 11 Release
A lot has happened since we published our last blog post six months ago. We got our first pro subscribers, we hired John who helps us with the docs, communication and community and we are all working full time on React Flow 🥳. Today we are releasing a new major version with lots of new features and very few breaking changes.
Read more16 November 2022
How we lost our slick new npm package name (and then got it back)
In 2019 we started building a library for building node based UIs, and decided to call it “React Flow.” It’s a nice name, so of course “reactflow” and “react-flow” were already taken. The best option we had for us was “react-flow-renderer,” so we took what we could get.
Read more