--why shows first level/depth dependents

[roymiloh]

Say I have the following graph:

a -> b -> c -> d (a depends on b and so on).

When I do qnm --why d, I'm getting c, which is fine - but I'd like to get the entire path until the direct dependency itself in some manner.

[ranyitz]

Thanks @roymiloh, this is a cool idea!

There is a small UX problem that needs to be solved, some packages are being downloaded because multiple packages depend on them, which means that the output would be a bit harder to present.

We could create some interactive mode that will let the user to explore and expand dependency trees dynamically.

If there is a nice way to preset the whole tree statically that could be also nice.

I'm open for ideas and PRs

[moshfeu]

If I understand correctly, it should behave the same as npm list [package], right?

For example:

> qnm serialize-javascript serialize-javascript

serialize-javascript
├── 2.1.2
└─┬ webpack
  └── 1.9.0

compare to

> npm list serialize-javascript

my-package@0.1.0 /path/to/my-package
└─┬ react-scripts@3.3.0
  ├─┬ terser-webpack-plugin@2.2.1
  │ └── serialize-javascript@2.1.2 
  └─┬ webpack@4.41.2
    └─┬ terser-webpack-plugin@1.4.1
      └── serialize-javascript@1.9.0

[ranyitz]

The problem with the npm ls tree is that it doesn't show the versions that you have on the file system. Meaning that you don't know which version is located on the root node_modules and which version is nested inside of other modules' node_modules directory.

[moshfeu]

Have not tested it. So seems like qnm should take both of the worlds..

[ranyitz]

You're right, finding good ways to show the full tree would give a lot of value.