Posts tagged: coding, page 3

June 10, 2026

Introducing vitest-command-line

Testing command-line tools is deceptively hard - hanging processes, lost stderr, temp file juggling, and unreadable failures. I built vitest-command-line to make CLI testing in Vitest simple and robust.

June 9, 2026

React Server Components

Part of the React Internals Series

Server rendering can send HTML early and still ship component code to the browser. React Server Components change which code ships at all—but their payload is not HTML, and interactive components still need hydration.

June 8, 2026

Server-Side Rendering and Hydration

Part of the React Internals Series

Server-rendered HTML can appear before the app is interactive, but hydration still renders your components in the browser. Reusing that HTML depends on the first client render matching—a timestamp or browser-only value can break the agreement.

June 6, 2026

React Spring: Motion Between Renders

Part of the React Internals Series

A menu fade driven by setState sends every frame through React's render-commit loop. React Spring moves those intermediate writes straight to the host—but it needs a real host instance, and browser layout can still drop frames.

June 6, 2026

An Introduction to Tailwind CSS

Tailwind makes JSX busier so styling is easier to find. Its utility classes also avoid runtime style generation—a trade that becomes more consequential when React components can stay entirely on the server.

June 5, 2026

One Reconciler, Many Renderers

Part of the React Internals Series

React can update a button, a native view, or a Three.js mesh without knowing how to create any of them. The renderer supplies that knowledge—and determines what your refs actually expose.

June 5, 2026

An Introduction to CSS

A CSS rule can match and still lose; a hidden element can still take up space. Following the browser from selectors to boxes and layout makes these beginner surprises easier to diagnose.

June 4, 2026

React Skips: How Rendering Optimization Works

Part of the React Internals Series

A React component can render without changing the DOM, and memoization can cost more than rerendering. Understanding which work React actually skips makes the difference between a useful optimization and extra bookkeeping.

June 3, 2026

React Scheduling

Part of the React Internals Series

React can abandon a render without changing a pixel on screen. Lanes, transitions, and Suspense let urgent input run ahead of expensive work while React prepares the next UI and keeps the committed tree intact.

June 2, 2026

React Fiber Tree: The Virtual DOM

Part of the React Internals Series

React can prepare a new screen, pause, and throw the work away while the current UI stays intact. The same fiber structure explains why keys preserve list state and why hook order cannot change.

June 1, 2026

React Prerequisites

Part of the React Internals Series

Calling a component, updating the DOM, and painting pixels are three different events. Keeping them separate explains why React requires pure renders—and why choosing between useEffect and useLayoutEffect affects what users see.

May 15, 2026

node-prewarm: CLI for Node 25's Compile Cache

New in Node 25 is the node compile cache, which can deliver a 20% to 30% boost in server start-up time. I built `node-prewarm` to make that practical on real projects with minimal changes.