Project packages - increase scope

[sebasmonia]

Right now I'm just listing top level packages (ie what was explicitly added).
Including transitive packages makes the list huge.

1. are transitive packages needed?
2. include a binding to list only deprecated packages
3. include a binding to list only packages that are outdated
4. a. provide a path to update them

[sebasmonia]

There is now an option to list transitive packages, but not to add/remove them.

[sebasmonia]

We can add and remove packages, removing transitives doesn't make any sense (it will fail unless you remove the parent first, which in turn removes the transitive package).

[sebasmonia]

Updated target:

• include a binding to list only deprecated packages
• include a binding to list only packages that are outdated
• provide a path to update the above

[mcraveiro]

Thanks for a great mode, I'm beginning to use it more and more :-) The ability to include and exclude transitive packages is quite helpful as some times you need one or the other, I must say.

[sebasmonia]

Glad you find it useful!

You can list now transitive packages, but the CLI won't let you remove them unless you remove the parent anyway.

I guess we could have a binding to convert a transitive package to an explicit reference.

[mcraveiro]

Actually, I just got my head around the comments above and I think I see what you mean, using L is great but then you end up listing all of the transitive packages for the solution which is a lot in my case. My typical use case tends to be more comparing two projects, one that works and one that doesn't :-) it would be great to have this option at project level...

[sebasmonia]

Hi again @mcraveiro! The listing including transitive packages works at project level, not solution. Please let me know if there's some confusion or something to add to the docs to make things more clear.