[Feature Request] a way to specify NuGet dependencies of a Unity package

[CDTR-MattConroy]

I have a lot of internal Unity packages and some of them have NuGet dependencies. At the moment when I install, say, Logging, which relies on Microsoft.Extensions.Logging and Serilog.Sinks.File, I get errors because the NuGet dependencies do not exist. I have to install the dependencies manually into the consuming project. This gets complex quickly when there are packages that rely on packages that rely on NuGet packages etc.

I would love to be able to specify in the package.json for the Unity package which NuGet dependencies are required as well as Unity dependencies. This should probably be a custom property in package.json, separate to the existing dependencies property.
This could be queried by NuGetForUnity for every installed package (and their dependencies) and add them to the consuming project's packages as transitive dependencies.

This would be a huge boon for us, I hope the above description makes sense. Thanks!

[Thaina]

Is this the same feature?

#735

[CDTR-MattConroy]

Yes I believe so. It sounds like I'm coming at it from the other direction though, as a UPM package author, I want to be able to specify my NuGet dependencies.