26 docs tagged with "React"

The library you choose determines the maintenance burden you carry. Copy-paste ownership (shadcn) trades update convenience for full control. Package dependencies trade control for automatic updates.

Web component animation.

Eth Hooks Overview

Place state where the server can read it. Hydration mismatches disappear.

Why abstract forms? Because browser defaults sabotage validation.

Sending email with nextjs.

Middleware allows you to run code before a request is completed.

Where is the bottleneck — render, network, or bundle?

Calendars look simple. Then you add timezones, recurring events, drag-to-reschedule, and multi-user availability. Complexity explodes.

A chart that lies is worse than no chart. Choose the library that makes honest data easy and misleading data hard.

Components are the unit of reuse. Get the abstraction boundary wrong and you carry the cost in every file that imports it.

React Hooks best practices and custom use cases.

Memory leaks are invisible until they crash production. The app works in development. It dies at scale.

<iframe

Libraries and best practices for fetching, caching, synchronizing and updating server state

There is not an opinionated path for state management in React compared to alternative frameworks.

Zustand simplifies state management.

React and Typescript

<iframe

React useContext

Provides us an opportunity to write code that may have side effects on the application.

Refs are escape hatches. Try to avoid using them where possible.

Snippets

SVGs scale without pixelation. They also bloat your bundle if you inline them carelessly.

Forms are where users meet friction. Every field is a chance to lose them.

Easy to use and highly customizable React tables.