DocsReference

CLI and deno.json quick reference

Common Deno commands, configuration ownership, tasks, imports, and troubleshooting order

Command map

GoalCommand
Version / helpdeno --version / deno help <command>
Initializedeno init / deno init --serve
Run an entrydeno run [permissions] main.ts
Run a taskdeno task <name>
Add / remove dependencydeno install <pkg> / deno uninstall <pkg>
Reproducible CI installdeno ci / deno ci --prod
List / audit dependenciesdeno list / deno audit
Inspect module graphdeno info main.ts
Format / lintdeno fmt / deno lint
Type-checkdeno check main.ts
Test / coveragedeno test / deno test --coverage
Generate docsdeno doc
Compile / bundledeno compile / deno bundle
Build a desktop appdeno desktop (2.9+)
Deploy to Deno Deploydeno deploy
Publish to JSRdeno publish --dry-run / deno publish
Upgrade Denodeno upgrade

Minimal configuration

{
  "tasks": {
    "dev": "deno run --watch --allow-net --allow-env=PORT main.ts",
    "check": "deno fmt --check && deno lint && deno check **/*.ts && deno test"
  },
  "imports": {
    "@std/assert": "jsr:@std/assert@^1.0.0"
  },
  "lint": { "rules": { "tags": ["recommended"] } },
  "fmt": { "lineWidth": 100 }
}

Add only keys verified against the current deno.json reference and required by the repository.

Troubleshooting order

  1. Record deno --version, OS, and architecture.
  2. Identify the effective deno.json(c) and workspace root. Use deno info <entry> and deno task to observe actual resolution and tasks instead of guessing merged configuration.
  3. Inspect deno task and deno info <entry>; do not guess the entry or graph.
  4. Separate permission denial, module resolution, type error, runtime exception, and platform failure.
  5. Build a minimal reproduction, then query current official docs and issues.

Official references: CLI and deno.json.

Type to search all documentation.