Start here
A few useful paths through the archive.
These are short, practical reading paths built around real jobs. Start with the problem in front of you, not the oldest article in the list.
Release workflow
Ship changes without guessing
A practical route through preview checks, Worker configuration, and the small failures that only show up after deploy.
You end up with a repeatable release check instead of a pile of browser tabs.
- 01Compare Preview and Production Before You MergeCatch preview deployment drift in status codes, redirects, headers, cookie attributes, canonical URLs, and robots metadata before production.
- 02Lint wrangler.jsonc in GitHub Actions Before You DeployRun Cloudflare Workers config checks in GitHub Actions, annotate exact Wrangler lines, scan monorepos, and upload SARIF when you need it.
- 03Your Wrangler Staging Environment May Share Production DataCheck whether Wrangler staging is missing bindings or points at production resources, then isolate D1 and make every deploy target explicit.
Maintenance
Upgrade the stack without a surprise
Useful when a runtime, package manager, framework, or lint setup changes underneath an otherwise healthy project.
You can separate a real compatibility problem from a noisy install warning and test the right path.
- 01Node 20 Is EOL: Find Every Runtime Pin Before a Failed DeployNode 20 is EOL. Audit package metadata, CI, Docker, and host settings, choose a supported target, then verify every runtime pin before a deploy fails.
- 02Run TypeScript 7 Without Breaking typescript-eslintFix TypeScript 7 ESLint peer conflicts and Cjs crashes by running TypeScript 7 beside the TypeScript 6 compatibility API, with a verified npm setup.
- 03pnpm 11 Ignored Your Overrides: Move Config Before CI Rewrites Itpnpm 11 moved project settings out of package.json. Migrate overrides and build policy to pnpm-workspace.yaml before CI rewrites your lockfile.
Next.js
Make App Router changes less painful
Migration notes and focused fixes for route params, CSS, caching, and the things that often get missed outside the page component.
You get a clearer upgrade path and a better checklist for catching the quiet regressions.
- 01Migrate Next.js Pages Router to App Router Without Breaking EverythingA detailed Pages Router to App Router migration guide covering layouts, route structure, Server Components, caching, metadata, forms, auth, testing, and a safe rollout.
- 02Fix “params should be awaited” in Next.js App RouterFix the Next.js “params should be awaited” error in App Router pages and layouts, with safe TypeScript patterns and a migration checklist.
- 03Next.js 16 Cache Components: Choose cacheLife Before You Cache DataUse a clear freshness contract for Next.js 16 Cache Components: decide what can be shared, set cacheLife deliberately, tag reads, and test invalidation.
AI work
Add AI without losing the plot
A sensible starting point for AI-assisted code, app builders, and deciding what still needs a proper human review.
You can keep ownership, permissions, and release checks visible while still moving quickly.
- 01Review AI-Generated Code Before It Reaches ProductionA practical review workflow for AI-assisted changes: define the contract, inspect the diff, test failure paths, and check security-sensitive boundaries.
- 02Do You Own Your Lovable Code? GitHub Sync and an Exit PlanUnderstand what Lovable GitHub sync preserves, what remains outside the repository, and how to test a real code, data, and hosting exit plan.
- 03Can Lovable Build a Production App? A Developer’s Release ChecklistUse this developer checklist to review Git ownership, authorization, RLS, secrets, tests, monitoring, and rollback before launching a Lovable app.