You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, only dependencies mentioned in package.json are included in the output. This is similar to npm ls.
A new option -t / --transitive could be implemented for including transitive dependencies (dependencies of dependencies). This would be similar to npm ls --all.
The text was updated successfully, but these errors were encountered:
Hey, thanks for all the suggestions. I don't have ample time to work on them at the moment unfortunately, but I think they are all quite reasonable.
As for transitive dependencies, I think it would be quite hard to implement because we would have to do a lot of dependency resolution to even create something remotely accurate - basically we would have to ping npm for all the deps, then all their deps, and recursively until we reach an end, and then also resolve what versions are applicable for each branch. It feels like a very heavy and complicated process, and might be best left to package managers to do.
Right now, only dependencies mentioned in package.json are included in the output. This is similar to
npm ls
.A new option
-t
/--transitive
could be implemented for including transitive dependencies (dependencies of dependencies). This would be similar tonpm ls --all
.The text was updated successfully, but these errors were encountered: