hayatosc/dotfiles/hono-best-practices

Hono Best Practices

Preserve the inference chain from route definitions to the RPC client and validate external input at runtime. Follow the repository's runtime, validator, and test setup.

Required Baseline

• Keep the typed result of chained route definitions and export its type for RPC. Mount feature routers with app.route() rather than losing their inferred route types.
• Prefer inline route handlers. Before extracting handlers, read routing.md and preserve path, validator, and middleware inference.
• Type bindings and context variables with the app's Env; ensure middleware initializes variables before handlers use them.
• Validate external input with the project's validator and consume the validated result. Set the matching Content-Type in JSON/form request tests.
• Register middleware in the intended scope and order. Keep authentication and error handling intact when reorganizing routes.

Select the Relevant Reference

Read the reference that resolves the current question; these are independent routes, not a reading checklist. Check the installed version and official Hono docs when an API or runtime detail is uncertain.

Common Failure Signals

• Missing RPC routes: check whether the exported value retains the chained route type.
• Unknown context variables: check the Env generic and the middleware that initializes them.
• Empty JSON or form bodies: check the request's Content-Type.
• Weakened path parameter inference: check detached handlers and factory boundaries.

Complete the affected behavior and use the relevant project checks. For RPC changes, establish both server behavior and client type inference; do not introduce a new dependency or reshape unrelated routes merely to match an example.