Static rendering and server rendering both involve rendering HTML for each of your app's pages – but there's one major difference between them...
Build big, fast, CDN-delivered websites with great SEO & SMO, and all with vanilla create-react-app.
Headless components are a great new way to separate presentation and control logic. But what if you don't want to pick and place all the render function's props manually?
defaultProps object on React components doesn't have access to
this.props. So how can I make default props depend on other props?
React makes it easy to pass children to reusable components. But what if those children need to receive data from the component that renders them?
Before you replace Redux's
<Provider> component with React's new context API, there's a thing or two that you should know about performance.
Since Redux was created in 2015, its
<Provider> component has always used React's Context API. So how can Context replace Redux?
Dive deep into React's four approaches to conditional rendering, then test your knowledge by building a multi-step regisration wizard.
- 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
- 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?