v1.2.5 — Fix Deno Deploy 'entrypoint not found' error

What was broken

Users deploying the worker on Deno Deploy got:

Entrypoint at '/tmp/build/src/main.ts' not found

Deno Deploy project mode looks for main.ts (or src/main.ts) as the entrypoint by default. The previous proxy.deno.js was a JavaScript file with the wrong name — Deno Deploy couldn't find the expected entrypoint.

What's fixed

• Created worker/main.ts — TypeScript with full type annotations (Deno's type checker requires explicit types; .js files with implicit any fail deno check)
• Also created worker/src/main.ts as a fallback (in case Deno Deploy looks there instead)
• Added worker/deno.json with entrypoint: "main.ts" to make the entrypoint explicit
• Updated worker/README.md with clearer instructions emphasizing the Playground method (which avoids the entrypoint issue entirely) + troubleshooting for the error

Verified: deno lint and deno check both pass with 0 errors. Runtime test confirms health check + POST search + GET persisted-query all work.

What you should do

If you're deploying on Deno Deploy, use the Playground method (not "New Project"):

1. Go to https://dash.deno.com → "New Project" → "Playground" (top-right)
2. Delete the default code
3. Paste the contents of worker/main.ts
4. Click "Save & Deploy"

The Playground doesn't have a build step, so the entrypoint issue doesn't apply.

If you prefer the GitHub repo method, fork SNI and Deno Deploy will auto-detect main.ts at the repo root.

Install

pip install --upgrade sni-cli

Full changelog: v1.2.4...v1.2.5