File Explorer

1.TH "NPM-LL" "1" "February 2026" "NPM@11.11.0" ""2.SH "NAME"3\fBnpm-ll\fR - List installed packages4.SS "Synopsis"5.P6.RS 27.nf8npm ll \[lB]\[lB]<@scope>/\[rB]<pkg> ...\[rB]9 10alias: la11.fi12.RE13.SS "Description"14.P15List installed packages16.SS "Configuration"17.SS "\fBall\fR"18.RS 019.IP \(bu 420Default: false21.IP \(bu 422Type: Boolean23.RE 024 25.P26When running \fBnpm outdated\fR and \fBnpm ls\fR, setting \fB--all\fR will show all outdated or installed packages, rather than only those directly depended upon by the current project.27.SS "\fBjson\fR"28.RS 029.IP \(bu 430Default: false31.IP \(bu 432Type: Boolean33.RE 034 35.P36Whether or not to output JSON data, rather than the normal output.37.RS 038.IP \(bu 439In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.40.RE 041 42.P43Not supported by all npm commands.44.SS "\fBlong\fR"45.RS 046.IP \(bu 447Default: false48.IP \(bu 449Type: Boolean50.RE 051 52.P53Show extended information in \fBls\fR, \fBsearch\fR, and \fBhelp-search\fR.54.SS "\fBparseable\fR"55.RS 056.IP \(bu 457Default: false58.IP \(bu 459Type: Boolean60.RE 061 62.P63Output parseable results from commands that write to standard output. For \fBnpm search\fR, this will be tab-separated table format.64.SS "\fBglobal\fR"65.RS 066.IP \(bu 467Default: false68.IP \(bu 469Type: Boolean70.RE 071 72.P73Operates in "global" mode, so that packages are installed into the \fBprefix\fR folder instead of the current working directory. See npm help folders for more on the differences in behavior.74.RS 075.IP \(bu 476packages are installed into the \fB{prefix}/lib/node_modules\fR folder, instead of the current working directory.77.IP \(bu 478bin files are linked to \fB{prefix}/bin\fR79.IP \(bu 480man pages are linked to \fB{prefix}/share/man\fR81.RE 082 83.SS "\fBdepth\fR"84.RS 085.IP \(bu 486Default: \fBInfinity\fR if \fB--all\fR is set; otherwise, \fB0\fR87.IP \(bu 488Type: null or Number89.RE 090 91.P92The depth to go when recursing packages for \fBnpm ls\fR.93.P94If not set, \fBnpm ls\fR will show only the immediate dependencies of the root project. If \fB--all\fR is set, then npm will show all dependencies by default.95.SS "\fBomit\fR"96.RS 097.IP \(bu 498Default: 'dev' if the \fBNODE_ENV\fR environment variable is set to 'production'; otherwise, empty.99.IP \(bu 4100Type: "dev", "optional", or "peer" (can be set multiple times)101.RE 0102 103.P104Dependency types to omit from the installation tree on disk.105.P106Note that these dependencies \fIare\fR still resolved and added to the \fBpackage-lock.json\fR or \fBnpm-shrinkwrap.json\fR file. They are just not physically installed on disk.107.P108If a package type appears in both the \fB--include\fR and \fB--omit\fR lists, then it will be included.109.P110If the resulting omit list includes \fB'dev'\fR, then the \fBNODE_ENV\fR environment variable will be set to \fB'production'\fR for all lifecycle scripts.111.SS "\fBinclude\fR"112.RS 0113.IP \(bu 4114Default:115.IP \(bu 4116Type: "prod", "dev", "optional", or "peer" (can be set multiple times)117.RE 0118 119.P120Option that allows for defining which types of dependencies to install.121.P122This is the inverse of \fB--omit=<type>\fR.123.P124Dependency types specified in \fB--include\fR will not be omitted, regardless of the order in which omit/include are specified on the command-line.125.SS "\fBlink\fR"126.RS 0127.IP \(bu 4128Default: false129.IP \(bu 4130Type: Boolean131.RE 0132 133.P134Used with \fBnpm ls\fR, limiting output to only those packages that are linked.135.SS "\fBpackage-lock-only\fR"136.RS 0137.IP \(bu 4138Default: false139.IP \(bu 4140Type: Boolean141.RE 0142 143.P144If set to true, the current operation will only use the \fBpackage-lock.json\fR, ignoring \fBnode_modules\fR.145.P146For \fBupdate\fR this means only the \fBpackage-lock.json\fR will be updated, instead of checking \fBnode_modules\fR and downloading dependencies.147.P148For \fBlist\fR this means the output will be based on the tree described by the \fBpackage-lock.json\fR, rather than the contents of \fBnode_modules\fR.149.SS "\fBunicode\fR"150.RS 0151.IP \(bu 4152Default: false on windows, true on mac/unix systems with a unicode locale, as defined by the \fBLC_ALL\fR, \fBLC_CTYPE\fR, or \fBLANG\fR environment variables.153.IP \(bu 4154Type: Boolean155.RE 0156 157.P158When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs.159.SS "\fBworkspace\fR"160.RS 0161.IP \(bu 4162Default:163.IP \(bu 4164Type: String (can be set multiple times)165.RE 0166 167.P168Enable 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.169.P170Valid values for the \fBworkspace\fR config are either:171.RS 0172.IP \(bu 4173Workspace names174.IP \(bu 4175Path to a workspace directory176.IP \(bu 4177Path to a parent workspace directory (will result in selecting all workspaces within that folder)178.RE 0179 180.P181When set for the \fBnpm init\fR 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.182.P183This value is not exported to the environment for child processes.184.SS "\fBworkspaces\fR"185.RS 0186.IP \(bu 4187Default: null188.IP \(bu 4189Type: null or Boolean190.RE 0191 192.P193Set to true to run the command in the context of \fBall\fR configured workspaces.194.P195Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:196.RS 0197.IP \(bu 4198Commands that operate on the \fBnode_modules\fR tree (install, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, \fIunless\fR one or more workspaces are specified in the \fBworkspace\fR config.199.RE 0200 201.P202This value is not exported to the environment for child processes.203.SS "\fBinclude-workspace-root\fR"204.RS 0205.IP \(bu 4206Default: false207.IP \(bu 4208Type: Boolean209.RE 0210 211.P212Include the workspace root when workspaces are enabled for a command.213.P214When false, specifying individual workspaces via the \fBworkspace\fR config, or all workspaces via the \fBworkspaces\fR flag, will cause npm to operate only on the specified workspaces, and not on the root project.215.P216This value is not exported to the environment for child processes.217.SS "\fBinstall-links\fR"218.RS 0219.IP \(bu 4220Default: false221.IP \(bu 4222Type: Boolean223.RE 0224 225.P226When set file: protocol dependencies will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.227.SS "See Also"228.RS 0229.IP \(bu 4230npm help "help config"231.RE 0232