Fixes

Real bugs from real indie projects, traced to root cause and solved.

19 fixes · all from production

Payments & billing 2

Supabase & data 5

Cloudflare & deploy 6

CloudflareWindows

When wrangler dies behind a corporate proxy, use the API

Wrangler and other vendor CLIs hang or throw TLS errors behind a corporate proxy that intercepts HTTPS. Skip the CLI and drive the Cloudflare REST API directly with curl and a scoped token.

2 min read →

CloudflarePages

A Pages custom domain added by API gets stuck on 'CNAME record not set'

Attach a custom domain to a Cloudflare Pages project through the API and it can sit at pending forever. The dashboard auto-creates the DNS record; the API doesn't, and a Pages-scoped token can't either.

2 min read →

CloudflarePages

Your Cloudflare Pages env vars do nothing (Direct Upload vs Git build)

You set a PUBLIC_ variable in the Pages dashboard, redeploy, and the build still can't see it. The reason: a Direct Upload project builds in your CI, not on Cloudflare, so the dashboard env vars never reach the build.

2 min read →

CloudflareCI

Your Cloudflare build passes locally but silently fails in CI

A Vite alias that reached outside the repo root built fine locally but failed on Cloudflare Pages for weeks, while the old bundle kept serving.

2 min read →

ViteTypeScript

A stale vite.config.js silently overrode my vite.config.ts

Edits to vite.config.ts had no effect because a compiled vite.config.js sat next to it, and Vite loads the .js in preference to the .ts.

1 min read →

HostingWindows

Hosting public images from a locked-down Windows box

Behind a corporate proxy, wrangler and the throwaway upload hosts all failed. GitHub plus jsDelivr was the dependable free image host.

2 min read →

Windows & tooling 2

Marketing ops 1

More 3