https://michi-docs.vercel.app A client-side router built from first principles. No routing libraries, no framework abstractions, just the raw History API and React primitives. https://michi-docs.vercel.app/blog/per-route-error-boundaries-and-prefetch-on-hover https://michi-docs.vercel.app/blog/per-route-error-boundaries-and-prefetch-on-hover Two problems that show up once a router has real users hitting it: what happens when one route breaks, and what happens while a user is deciding whether to click. This post covers building per-route error boundaries with two separate error channels, and prefetch on hover that reuses the exact same loader pipeline instead of building a second one. Sun, 12 Jul 2026 00:00:00 GMT https://michi-docs.vercel.app/blog/layout-that-persists-and-data-that-arrives-before-you-do https://michi-docs.vercel.app/blog/layout-that-persists-and-data-that-arrives-before-you-do Continuing to build a client-side router from scratch. This post covers what happens after the basics: how nested routes keep your navbar mounted across navigations, why the Outlet pattern is just a context counter, and how data loaders flip fetch-on-render into render-as-you-fetch with parallel execution and race condition guards. Tue, 16 Jun 2026 00:00:00 GMT https://michi-docs.vercel.app/blog/what-happens-when-you-click-a-link-in-react https://michi-docs.vercel.app/blog/what-happens-when-you-click-a-link-in-react I'm building a client-side router from scratch to understand what React Router and TanStack Router do under the hood. This post walks through what I've found so far: the History API that makes navigation work without reloads, why useState breaks in concurrent mode, how route patterns become regex, and the `useSyncExternalStore` hook that ties it all together. Fri, 12 Jun 2026 00:00:00 GMT