@@ -39,34 +39,6 @@ dependencies, not the physical layout of your `node_modules` folder.
39
39
40
40
When run as ` ll ` or ` la ` , it shows extended information by default.
41
41
42
- ### Note: Design Changes Pending
43
-
44
- The ` npm ls ` command's output and behavior made a _ ton_ of sense when npm
45
- created a ` node_modules ` folder that naively nested every dependency. In
46
- such a case, the logical dependency graph and physical tree of packages on
47
- disk would be roughly identical.
48
-
49
- With the advent of automatic install-time deduplication of dependencies in
50
- npm v3, the ` ls ` output was modified to display the logical dependency
51
- graph as a tree structure, since this was more useful to most users.
52
- However, without using ` npm ls -l ` , it became impossible to show _ where_ a
53
- package was actually installed much of the time!
54
-
55
- With the advent of automatic installation of ` peerDependencies ` in npm v7,
56
- this gets even more curious, as ` peerDependencies ` are logically
57
- "underneath" their dependents in the dependency graph, but are always
58
- physically at or above their location on disk.
59
-
60
- Also, in the years since npm got an ` ls ` command (in version 0.0.2!),
61
- dependency graphs have gotten much larger as a general rule. Therefore, in
62
- order to avoid dumping an excessive amount of content to the terminal, `npm
63
- ls` now only shows the _top_ level dependencies, unless ` --all` is
64
- provided.
65
-
66
- A thorough re-examination of the use cases, intention, behavior, and output
67
- of this command, is currently underway. Expect significant changes to at
68
- least the default human-readable ` npm ls ` output in npm v8.
69
-
70
42
### Configuration
71
43
72
44
<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->
0 commit comments