npm-ll(1) npm-ll(1)
NAME
npm-ll - List installed packages
Synopsis
npm ll [[<@scope>/]<pkg> ...]
alias: la
Description
List installed packages
Configuration
all
o Default: false
o Type: Boolean
When running npm outdated and npm ls, setting --all will show all
outdated or installed packages, rather than only those directly
depended upon by the current project.
json
o Default: false
o Type: Boolean
Whether or not to output JSON data, rather than the normal output.
o In npm pkg set it enables parsing set values with JSON.parse()
before saving them to your package.json.
Not supported by all npm commands.
long
o Default: false
o Type: Boolean
Show extended information in ls, search, and help-search.
parseable
o Default: false
o Type: Boolean
Output parseable results from commands that write to standard output.
For npm search, this will be tab-separated table format.
global
o Default: false
o Type: Boolean
Operates in "global" mode, so that packages are installed into the
prefix folder instead of the current working directory. See npm help
folders for more on the differences in behavior.
o packages are installed into the {prefix}/lib/node_modules folder,
instead of the current working directory.
o bin files are linked to {prefix}/bin
o man pages are linked to {prefix}/share/man
depth
o Default: Infinity if --all is set; otherwise, 0
o Type: null or Number
The depth to go when recursing packages for npm ls.
If not set, npm ls will show only the immediate dependencies of the
root project. If --all is set, then npm will show all dependencies by
default.
omit
o Default: 'dev' if the NODE_ENV environment variable is set to
'production'; otherwise, empty.
o Type: "dev", "optional", or "peer" (can be set multiple times)
Dependency types to omit from the installation tree on disk.
Note that these dependencies are still resolved and added to the
package-lock.json or npm-shrinkwrap.json file. They are just not
physically installed on disk.
If a package type appears in both the --include and --omit lists, then
it will be included.
If the resulting omit list includes 'dev', then the NODE_ENV
environment variable will be set to 'production' for all lifecycle
scripts.
include
o Default:
o Type: "prod", "dev", "optional", or "peer" (can be set multiple
times)
Option that allows for defining which types of dependencies to install.
This is the inverse of --omit=<type>.
Dependency types specified in --include will not be omitted, regardless
of the order in which omit/include are specified on the command-line.
link
o Default: false
o Type: Boolean
Used with npm ls, limiting output to only those packages that are
linked.
package-lock-only
o Default: false
o Type: Boolean
If set to true, the current operation will only use the package-
lock.json, ignoring node_modules.
For update this means only the package-lock.json will be updated,
instead of checking node_modules and downloading dependencies.
For list this means the output will be based on the tree described by
the package-lock.json, rather than the contents of node_modules.
unicode
o Default: false on windows, true on mac/unix systems with a unicode
locale, as defined by the LC_ALL, LC_CTYPE, or LANG environment
variables.
o Type: Boolean
When set to true, npm uses unicode characters in the tree output. When
false, it uses ascii characters instead of unicode glyphs.
workspace
o Default:
o Type: String (can be set multiple times)
Enable running a command in the context of the configured workspaces of
the current project while filtering by running only the workspaces
defined by this configuration option.
Valid values for the workspace config are either:
o Workspace names
o Path to a workspace directory
o Path to a parent workspace directory (will result in selecting all
workspaces within that folder)
When set for the npm init command, this may be set to the folder of a
workspace which does not yet exist, to create the folder and set it up
as a brand new workspace within the project.
This value is not exported to the environment for child processes.
workspaces
o Default: null
o Type: null or Boolean
Set to true to run the command in the context of all configured
workspaces.
Explicitly setting this to false will cause commands like install to
ignore workspaces altogether. When not set explicitly:
o Commands that operate on the node_modules tree (install, update,
etc.) will link workspaces into the node_modules folder. - Commands
that do other things (test, exec, publish, etc.) will operate on
the root project, unless one or more workspaces are specified in
the workspace config.
This value is not exported to the environment for child processes.
include-workspace-root
o Default: false
o Type: Boolean
Include the workspace root when workspaces are enabled for a command.
When false, specifying individual workspaces via the workspace config,
or all workspaces via the workspaces flag, will cause npm to operate
only on the specified workspaces, and not on the root project.
This value is not exported to the environment for child processes.
install-links
o Default: false
o Type: Boolean
When set file: protocol dependencies will be packed and installed as
regular dependencies instead of creating a symlink. This option has no
effect on workspaces.
See Also
o npm help "help config"
NPM@11.11.0 February 2026 npm-ll(1)
npm 11.11.0 - Generated Mon Mar 2 07:20:37 CST 2026