chantastic
I've found it pretty capable for doubling my stories as Jest tests. For those using testing-library for component testing, it even acts like a GUI for those tests.
If you're interested, I threw together a little walkthru that show some of the ways I'm using it with Jest: https://github.com/chantastic/vite-react-jest-testing-librar...
Data Fetching with Suspense and Relay on Facebook.com
Everything You Need to Know about React Suspense Before React Conf [audio]
GitHub Staff Engineer Talks GitHub Package Registry Details and Plans
Build a Consultancy on React Native – An Interview with Jamon Holmgren
What Is Developer Advocacy? [audio]
What is TypeScript and what does it mean for React?
Creating the Scrabble Mechanical Keyboard. Interview with Cassidy Williams
Getting Hired as a Senior JavaScript Dev. Interview with Kyle Shevlin
React Core Team Discusses Suspense, Hooks, and the Future on React Podcast
Design Systems in React at GitHub on React Podcast
Promise Accessibility with Ryan Florence on Reach UI (React) on React Podcast
Supporting Open Source with Michael Jackson on React Podcast
Prepack and the Future of JavaScript Performance with Nikolai Tillmann (Podcast)
Component design patterns in React.js
The only thing I don't like about React is the rapid churn in architecture best-practices (Flux et al). This is in stark contrast to Ember—which nails conventions and tooling but is written far about vanilla JS.
We use React because components are a great abstraction for the web. React components are also very transportable, making them a great addition to integrated systems like Rails.
I like to focus on transferable skills. I don't want to be a Backbone/Ember/Angular/whatever developer. I want to be a good JavaScript developer. React makes that happen.