lil-dot-org

The static website for lil.org, hosted on Cloudflare Workers Static Assets.

Development

Install the pinned Wrangler version and start the local Worker:

npm ci
npm run dev

In another terminal, run the route smoke tests:

npm run smoke -- http://127.0.0.1:8787

npm run check validates the Worker bundle and static-asset manifest without deploying. npm run types regenerates the Cloudflare binding declarations after configuration changes.

Deployment

Wrangler reads authentication from CLOUDFLARE_API_TOKEN. Never print, commit, or add the token to a Wrangler configuration file.

npm run check
npm run preview
npm run smoke -- https://migration-lil-dot-org.lil-org.workers.dev
npm run deploy
npm run smoke -- https://lil.org --production

The migration preview alias uploads a version without moving production traffic. Production deploys attach the lil.org custom domain. Cloudflare Workers Builds also deploys main with npx wrangler deploy; non-production branch builds are intentionally disabled.

Routing

Static files are served directly by Workers Static Assets. src/worker.js preserves the former Amplify aliases and redirects:

• /privacy, /extension/*, /nft-folder-help/*, /pp, and the well-known Apple association path serve their corresponding repository assets.
• /support/*, /get/*, /x/*, /github/*, /guide-ios/*, and /update preserve the existing external redirects and query strings.
• Unknown extensionless paths gain a trailing slash; remaining unknown paths return the homepage body with status 404.

The zone-level Cloudflare redirect rule handles HTTP-to-HTTPS and www-to-apex canonicalization before requests reach the Worker.

Rollback

Before removing the previous origin, detach the Worker custom domain and restore the captured proxied apex DNS records to send traffic back to Amplify. After Amplify has been deleted, use Cloudflare deployment history:

npx wrangler versions list
npx wrangler rollback