Custom hooks are like mixins: they're a great way to share stateful and side-effectful functionality between components.
React's eaglerly awaited Concurrent Mode can vastly improve user experience, but it requires a stricter way of writing components.
Even old-school class components allow you to compose component state. Hooks just make your life far, far simpler.
Navi is a new kind of router for React. It lets you declaratively map URLs to content, even when that content is asynchronous.
Hooks are a brand new API with a lot of hype. But don't let that fool you –
useContext() is incredibly useful.
You know how
catch work, but what about
finally? Does it run after rethrown exceptions or
CSS-in-JS can be a huge win for maintainability. But for large statically rendered websites, plain CSS still has its place.
- 4 ways to pass children to React elements
- React Fragments in Practice – 4 real-world examples
- Using MDX with create-react-app 2
- Static vs. Server Rendering
- Navi: SEO & routing with vanilla create-react-app
- Demoboard: a live editor with every package on NPM
- Passing state to render props via React context
- How to conditionally set default props on React components
- How to pass data to a React component's props.children
- React context and performance
- When Context Replaces Redux
- 3 Anti-patterns for Conditional Rendering with React
- 9 React Guides That Stood The Test Of Time
- React Controller Components
- A React app with just one file
- Structuring React projects with CRUV
- HTML attributes vs. DOM properties
- CSS-in-JS security: the rascal's guide
- ES6 classes vs. function components: which to use?
- How do you separate components?
- When should I use arrow functions with React?
- How to integrate React into an existing app?