@cryptotaxi247 / documentation-1
Code Commits Issues Pulls Sessions CI/CD
update-search-sensitivity
@reggi/path-to-regexp dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2 dependabot/npm_and_yarn/main/eslint-10.4.0 dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0 dependabot/npm_and_yarn/main/proc-log-7.0.0 dependabot/npm_and_yarn/npm_and_yarn-826852524d dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2 deprecate-totp-2fa dhei/classic-tokens gat-bypass-2fa-docs jpg619/fix-accessibility-content-flow jpg619/version-bump-tar-2 kartykp/gat-bypass-2fa-docs kartykp/upgrade-path-to-regex main maitxn/version-bump-tar patch-1 reggi/cache-based-on-version reggi/dev-engines reggi/fix-transform-prettier reggi/overrides update-search-sensitivity
mdx 203 lines 6.4 KB
Raw
1 ---
2 title: npm-ll
3 section: 1
4 description: List installed packages
5 github_repo: npm/cli
6 github_branch: latest
7 github_path: docs/lib/content/commands/npm-ll.md
8 redirect_from:
9 - /cli-commands/ll
10 - /cli-commands/npm-ll
11 - /cli-documentation/cli-commands/ll
12 - /cli-documentation/cli-commands/npm-ll
13 - /cli-documentation/commands/ll
14 - /cli-documentation/commands/npm-ll
15 - /cli-documentation/ll
16 - /cli-documentation/npm-ll
17 - /cli-documentation/v11/cli-commands/ll
18 - /cli-documentation/v11/cli-commands/npm-ll
19 - /cli-documentation/v11/commands/ll
20 - /cli-documentation/v11/commands/npm-ll
21 - /cli-documentation/v11/ll
22 - /cli-documentation/v11/npm-ll
23 - /cli/cli-commands/ll
24 - /cli/cli-commands/npm-ll
25 - /cli/commands/ll
26 - /cli/commands/npm-ll
27 - /cli/ll
28 - /cli/npm-ll
29 - /cli/v11/cli-commands/ll
30 - /cli/v11/cli-commands/npm-ll
31 - /cli/v11/commands/ll
32 - /cli/v11/ll
33 - /cli/v11/npm-ll
34 - /commands/ll
35 - /commands/npm-ll
36 ---
37
38 ### Synopsis
39
40 ```bash
41 npm ll [[<@scope>/]<pkg> ...]
42
43 alias: la
44 ```
45
46 ### Description
47
48 List installed packages
49
50 ### Configuration
51
52 #### `all`
53
54 - Default: false
55 - Type: Boolean
56
57 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.
58
59 #### `json`
60
61 - Default: false
62 - Type: Boolean
63
64 Whether or not to output JSON data, rather than the normal output.
65
66 - In `npm pkg set` it enables parsing set values with JSON.parse() before saving them to your `package.json`.
67
68 Not supported by all npm commands.
69
70 #### `long`
71
72 - Default: false
73 - Type: Boolean
74
75 Show extended information in `ls`, `search`, and `help-search`.
76
77 #### `parseable`
78
79 - Default: false
80 - Type: Boolean
81
82 Output parseable results from commands that write to standard output. For `npm search`, this will be tab-separated table format.
83
84 #### `global`
85
86 - Default: false
87 - Type: Boolean
88
89 Operates in "global" mode, so that packages are installed into the `prefix` folder instead of the current working directory. See [folders](/cli/v11/configuring-npm/folders) for more on the differences in behavior.
90
91 - packages are installed into the `{prefix}/lib/node_modules` folder, instead of the current working directory.
92 - bin files are linked to `{prefix}/bin`
93 - man pages are linked to `{prefix}/share/man`
94
95 #### `depth`
96
97 - Default: `Infinity` if `--all` is set; otherwise, `0`
98 - Type: null or Number
99
100 The depth to go when recursing packages for `npm ls`.
101
102 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.
103
104 #### `omit`
105
106 - Default: 'dev' if the `NODE_ENV` environment variable is set to 'production'; otherwise, empty.
107 - Type: "dev", "optional", or "peer" (can be set multiple times)
108
109 Dependency types to omit from the installation tree on disk.
110
111 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.
112
113 If a package type appears in both the `--include` and `--omit` lists, then it will be included.
114
115 If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts.
116
117 #### `include`
118
119 - Default:
120 - Type: "prod", "dev", "optional", or "peer" (can be set multiple times)
121
122 Option that allows for defining which types of dependencies to install.
123
124 This is the inverse of `--omit=<type>`.
125
126 Dependency types specified in `--include` will not be omitted, regardless of the order in which omit/include are specified on the command-line.
127
128 #### `link`
129
130 - Default: false
131 - Type: Boolean
132
133 Used with `npm ls`, limiting output to only those packages that are linked.
134
135 #### `package-lock-only`
136
137 - Default: false
138 - Type: Boolean
139
140 If set to true, the current operation will only use the `package-lock.json`, ignoring `node_modules`.
141
142 For `update` this means only the `package-lock.json` will be updated, instead of checking `node_modules` and downloading dependencies.
143
144 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`.
145
146 #### `unicode`
147
148 - 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.
149 - Type: Boolean
150
151 When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs.
152
153 #### `workspace`
154
155 - Default:
156 - Type: String (can be set multiple times)
157
158 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.
159
160 Valid values for the `workspace` config are either:
161
162 - Workspace names
163 - Path to a workspace directory
164 - Path to a parent workspace directory (will result in selecting all workspaces within that folder)
165
166 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.
167
168 This value is not exported to the environment for child processes.
169
170 #### `workspaces`
171
172 - Default: null
173 - Type: null or Boolean
174
175 Set to true to run the command in the context of **all** configured workspaces.
176
177 Explicitly setting this to false will cause commands like `install` to ignore workspaces altogether. When not set explicitly:
178
179 - 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.
180
181 This value is not exported to the environment for child processes.
182
183 #### `include-workspace-root`
184
185 - Default: false
186 - Type: Boolean
187
188 Include the workspace root when workspaces are enabled for a command.
189
190 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.
191
192 This value is not exported to the environment for child processes.
193
194 #### `install-links`
195
196 - Default: false
197 - Type: Boolean
198
199 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.
200
201 ### See Also
202
203 - [npm help config](/cli/v11/commands/npm-config)