deno list
The deno list command prints the packages your project declares as
dependencies. It reads them from the imports in your
deno.json and from the dependencies
and devDependencies in your package.json, resolves each to the version
currently in use, and prints them grouped by package, similar to npm ls or
pnpm list.
It answers a different question than
deno info: deno info walks the module graph
from an entrypoint and reports every file it reaches, while deno list reports
what the project depends on straight from the manifest, without an entrypoint.
Usage Jump to heading
deno list [OPTIONS] [filters...]
By default deno list prints a flat table of your direct dependencies. Optional
positional filters narrow the output by package name and support wildcards and
! negation, the same matcher
deno outdated uses.
Options Jump to heading
| Option | Description |
|---|---|
--depth <N> |
Render the resolved dependency tree N levels deep, for both npm and JSR packages (read from the lockfile). |
--prod |
Show only production dependencies. |
--dev |
Show only development dependencies. |
--recursive |
Include the dependencies of every workspace member. |
Examples Jump to heading
List direct dependencies:
deno list
Show the dependency tree two levels deep:
deno list --depth 2
List only production dependencies whose name starts with @std/:
deno list --prod "@std/*"
listList the dependencies declared in deno.json / package.json
Options Jump to heading
--depthMaximum depth of the dependency tree to display (0 = direct dependencies only).
--devOnly list development dependencies.
--prodOnly list production dependencies.
--recursive, -rInclude all workspace members.
Last updated on