codekingpro/portable-devtools

1.TH "NPM-LL" "1" "April 2026" "NPM@11.13.0" ""
2.SH "NAME"
3\fBnpm-ll\fR - List installed packages
4.SS "Synopsis"
5.P
6.RS 2
7.nf
8npm ll \[lB]\[lB]<@scope>/\[rB]<pkg> ...\[rB]
9
10alias: la
11.fi
12.RE
13.SS "Description"
14.P
15List installed packages
16.SS "Configuration"
17.SS "\fBall\fR"
18.RS 0
19.IP \(bu 4
20Default: false
21.IP \(bu 4
22Type: Boolean
23.RE 0
24
25.P
26When 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 0
29.IP \(bu 4
30Default: false
31.IP \(bu 4
32Type: Boolean
33.RE 0
34
35.P
36Whether or not to output JSON data, rather than the normal output.
37.RS 0
38.IP \(bu 4
39In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR.
40.RE 0
41
42.P
43Not supported by all npm commands.
44.SS "\fBlong\fR"
45.RS 0
46.IP \(bu 4
47Default: false
48.IP \(bu 4
49Type: Boolean
50.RE 0
51
52.P
53Show extended information in \fBls\fR, \fBsearch\fR, and \fBhelp-search\fR.
54.SS "\fBparseable\fR"
55.RS 0
56.IP \(bu 4
57Default: false
58.IP \(bu 4
59Type: Boolean
60.RE 0
61
62.P
63Output 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 0
66.IP \(bu 4
67Default: false
68.IP \(bu 4
69Type: Boolean
70.RE 0
71
72.P
73Operates 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 0
75.IP \(bu 4
76packages are installed into the \fB{prefix}/lib/node_modules\fR folder, instead of the current working directory.
77.IP \(bu 4
78bin files are linked to \fB{prefix}/bin\fR
79.IP \(bu 4
80man pages are linked to \fB{prefix}/share/man\fR
81.RE 0
82
83.SS "\fBdepth\fR"
84.RS 0
85.IP \(bu 4
86Default: \fBInfinity\fR if \fB--all\fR is set; otherwise, \fB0\fR
87.IP \(bu 4
88Type: null or Number
89.RE 0
90
91.P
92The depth to go when recursing packages for \fBnpm ls\fR.
93.P
94If 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 0
97.IP \(bu 4
98Default: 'dev' if the \fBNODE_ENV\fR environment variable is set to 'production'; otherwise, empty.
99.IP \(bu 4
100Type: "dev", "optional", or "peer" (can be set multiple times)
101.RE 0
102
103.P
104Dependency types to omit from the installation tree on disk.
105.P
106Note 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.P
108If a package type appears in both the \fB--include\fR and \fB--omit\fR lists, then it will be included.
109.P
110If 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 0
113.IP \(bu 4
114Default:
115.IP \(bu 4
116Type: "prod", "dev", "optional", or "peer" (can be set multiple times)
117.RE 0
118
119.P
120Option that allows for defining which types of dependencies to install.
121.P
122This is the inverse of \fB--omit=<type>\fR.
123.P
124Dependency 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 0
127.IP \(bu 4
128Default: false
129.IP \(bu 4
130Type: Boolean
131.RE 0
132
133.P
134Used with \fBnpm ls\fR, limiting output to only those packages that are linked.
135.SS "\fBpackage-lock-only\fR"
136.RS 0
137.IP \(bu 4
138Default: false
139.IP \(bu 4
140Type: Boolean
141.RE 0
142
143.P
144If set to true, the current operation will only use the \fBpackage-lock.json\fR, ignoring \fBnode_modules\fR.
145.P
146For \fBupdate\fR this means only the \fBpackage-lock.json\fR will be updated, instead of checking \fBnode_modules\fR and downloading dependencies.
147.P
148For \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 0
151.IP \(bu 4
152Default: 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 4
154Type: Boolean
155.RE 0
156
157.P
158When 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 0
161.IP \(bu 4
162Default:
163.IP \(bu 4
164Type: String (can be set multiple times)
165.RE 0
166
167.P
168Enable 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.P
170Valid values for the \fBworkspace\fR config are either:
171.RS 0
172.IP \(bu 4
173Workspace names
174.IP \(bu 4
175Path to a workspace directory
176.IP \(bu 4
177Path to a parent workspace directory (will result in selecting all workspaces within that folder)
178.RE 0
179
180.P
181When 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.P
183This value is not exported to the environment for child processes.
184.SS "\fBworkspaces\fR"
185.RS 0
186.IP \(bu 4
187Default: null
188.IP \(bu 4
189Type: null or Boolean
190.RE 0
191
192.P
193Set to true to run the command in the context of \fBall\fR configured workspaces.
194.P
195Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:
196.RS 0
197.IP \(bu 4
198Commands 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 0
200
201.P
202This value is not exported to the environment for child processes.
203.SS "\fBinclude-workspace-root\fR"
204.RS 0
205.IP \(bu 4
206Default: false
207.IP \(bu 4
208Type: Boolean
209.RE 0
210
211.P
212Include the workspace root when workspaces are enabled for a command.
213.P
214When 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.P
216This value is not exported to the environment for child processes.
217.SS "\fBinstall-links\fR"
218.RS 0
219.IP \(bu 4
220Default: false
221.IP \(bu 4
222Type: Boolean
223.RE 0
224
225.P
226When 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 0
229.IP \(bu 4
230npm help "help config"
231.RE 0
232