Nuget dependency management is a nightmare for my team. Mostly because there's usually only one package for a given problem, and you're always at their mercy. I

Nuget dependency management is a nightmare for my team. Mostly because there's usually only one package for a given problem, and you're always at their mercy. I suppose it's a community issue, because npm packages I seem to find few complications. Also, I always find plenty of documentation/tutorials/friendly community to help with the package, and never anyone expecting money for a out-of-date pdf generator that works with tooth-picks and bubble gum holding it together (for example). The manager in VS has gotten better, but it's still far more cumbersome than a cli.