
How I made loke.dev easier for AI agents to use
A practical look at the routes, APIs, DNS, and checks I added so AI agents can find and use loke.dev without guessing.
Field notes / The archive
A small set of practical guides for developers and small teams building, shipping, and fixing web software.

A practical look at the routes, APIs, DNS, and checks I added so AI agents can find and use loke.dev without guessing.

AI can help you investigate, draft, and review. The useful part starts when you turn its output into a short, checked answer you can stand behind.

Find why a Next.js App Router page or Server Action feels slow, then fix waterfalls, duplicate queries, uncached fetches, and slow post-action refreshes.

A practical way to find the first server and browser difference behind a Next.js hydration error, with fixes for dates, browser APIs, HTML nesting, and extensions.

A hands-on fix for the Next.js 16.3 ENOENT trace-file error on Vercel, with checks for Docker and self-hosted standalone builds.

Fix TypeScript 7 ESLint peer conflicts and Cjs crashes by running TypeScript 7 beside the TypeScript 6 compatibility API, with a verified npm setup.

Triage the sharp advisory in Next.js 16.2, apply a package-manager override carefully, and test the real image path before deploying on Vercel.

Fix missing dated Cloudflare Workers type entrypoints after v5, migrate app types to wrangler types, and keep generated declarations current in CI.

Node 20 is EOL. Audit package metadata, CI, Docker, and host settings, choose a supported target, then verify every runtime pin before a deploy fails.

Catch preview deployment drift in status codes, redirects, headers, cookie attributes, canonical URLs, and robots metadata before production.