expose package resolution information

[rmehri01]

Hey, first just wanted to say thanks, uv is a really great tool!

We're trying to use torch cpu by default on Replit, including for transitive dependencies, and have run into a few of the other issues that are open such as #9647. While those are being fixed, we were wondering if there is an easy way to expose package resolution information so that we can work around it?

As far as we know the closest thing is uv tree but that requires the package to be installed so we'd have to install cuda torch, do uv tree, and then override the torch version with cpu, which isn't ideal.

[charliermarsh]

Thanks!

What kind of information are you looking for? Like, what is your ideal API? You want to provide a package + version, and see the METADATA file?

[rmehri01]

Yeah that sounds good, as a concrete example, something we want to be able to deal with is if someone wants to install easyocr then we can see what that depends on, which includes a certain torchvision version and then try to install the cpu version for that explicitly instead as a workaround. Something like uv resolve foo>=1.2.3,<2 --format json that emits some subset of the METADATA and possibly some information about why a particular version and index was chosen would be nice.