Fair enough. Presumably I can query a script first somehow to see what the dependency tree is going to look like?

Well for regular dotnet project there is `dotnet list` that allow that, I don't know how it will look c# script file, probably the same.

From what I've read of this preview `dotnet list` works as expected. Under the hood it supposedly builds a mini-project file so that most of the `dotnet` cli works as expected. It also provides an "eject button" to build the csproj from the script file `dotnet project convert`.