starter

Summary After PR #90 migrated the templates from to wrangler's dynamic (which I think was the right call — config-aware types are genuinely more accurate), users who rely on Hono's type vending features hit immediate type errors after scaffolding, because doesn't exist until is manually run. The README mentions , but missing this step results in silent breakage that's hard to diagnose, and easy to skip. Reproduction Using (same applies to and ): Replace with a minimal type-vending example: Run typecheck: Hono's chain inference produces because no global / type is available in the project — has only and . Fix verification Once is generated, type vending works as expected. Why this matters Real-world users who would hit this: Anyone using RPC client → client types resolve to Anyone using 's → fails with Anyone running in CI → CI fails on a fresh scaffold For comparison, sibling templates handle this seamlessly out-of-the-box: : in devDependencies / : + : nothing — relies on the user knowing to run Possible approaches I understand the rationale for PR #90 (config-aware types via is more accurate), so I'm not suggesting reverting it. Instead, options to close the UX gap: A. Add to template Pros: Covers initial install, teammate clones, CI environments, and updates Works across all package managers (npm/pnpm/yarn/bun) Smallest change — template-only, no CLI changes Cons: failures abort install (e.g., on Node < 22) B. Run from CLI after install Add a hook that runs for cloudflare templates after install. Pros: Keeps clean Cons: Doesn't help when teammates clone and run Doesn't help when changes Requires changes to itself C. Hybrid: A + / Combine A with / to also keep types fresh on every dev/build run. Personally I lean toward A as the simplest fix with the broadest coverage. Happy to open a PR once direction is decided. Side note**: an additional UX gotcha during reproduction — itself requires Node 22+. Users on Node 20 hit a secondary error () when manually running . Worth keeping in mind for the postinstall approach (postinstall would surface this earlier). cc @yusukebe @Thomascogez (referencing PR #90 context)