Digests » 265
this week's favorite
Put your detective hat on and embark upon a debugging murder mystery journey through React Nativeland.
In my recent article on TypeScript and React component patterns I’ve stated that I don’t use the built-in type React.FC<> but rather be explicit with typing children. I didn’t state why, and it sparked some interest. That’s why I want to elaborate a little bit.
The modern age of web development that includes modularized, encapsulated web components, has brought us a plethora of tools, technologies, frameworks, and libraries of all varieties. With every such tool that is created to simplify our lives as developers in the long run, there's also a catch we sometimes neglect to consider: the cost of maintenance and performance.
The biggest feature of React 17, as React team claims, is that there are no new features. This isn't however entirely true. In Babel 7.9.0, a new JSX transform was announced. It could only be used in experimental React releases. Until now!
Showcasing new product features to users or familiarizing them with some UI functionality in a web app can get tedious, especially when you want users to see a lot of things. In the following guide, you’ll learn how to proactively use product tours to onboard users into a new and complex UX, and how to familiarize them with UI functionality without boring them, using a typical React app.
Ever wondered how to test modals, Stripe, Redux, context, custom hooks? This free react testing masterclass is for you.