James K Nelson

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?

The 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?

You already know how to implement conditionally rendering with React: just use JavaScript! This gives you a huge amount of power... to shoot yourself in the foot.

React comes with a boatload of buzzwords. Redux and GraphQL and Webpack and JSX and how am I supposed to get anything done when keeping up with the ecosystem is a full time job in itself?

Where do your components go? Where should you put business logic? Where do higher order components fit in? And even if your structure feels right now, how do you know that it won’t feel wrong later?

Luckily, React forms don’t have to be awkward. In fact, they can be downright easy. And the trick is simple: you just need to understand that form state isn’t like other state.

While React’s component system is great for creating view components, it can’t solve everything. And in particular, it can’t solve state.