Deno

Use Deno's official documentation as the source of truth. Check deno --version and the project's configuration before choosing APIs or flags; current online documentation may describe a newer runtime. Verify uncertain or version-sensitive behavior against the relevant page and local deno <command> --help. Cite the specific documentation used.

Start with the existing project

• Inspect deno.json / deno.jsonc, package.json, lockfiles, workspace members, and existing tasks. Preserve the project's dependency and tooling conventions.
• For a new Deno project, use deno init when its starter fits. Do not add a transpiler, bundler, test framework, or formatter merely to run TypeScript.
• Prefer built-in Web APIs (fetch, Request, Response, streams, Web Crypto) and Deno APIs before adding dependencies.
• Running TypeScript does not imply type checking. Run deno check explicitly.