Suggestion: Finer grained module dependencies

[jollytoad]

Many packages are treated as libraries, where individual modules are imported, rather than a single entrypoint.

JSR Dependencies currently only displays the high-level overview of packages as dependencies, and doesn't reflect that only certain modules of a package are actually depended on.

I think Dependencies really needs to reflect this, to inform the viewer of the true nature of the dependency, and whether its just of a particular module or of a whole package.

Take this view for example: https://jsr.io/@http/fns/dependencies

It just lists out a set of packages, misleadingly implying that it depends on the whole of each package, yet the majority of imports for this packages is actually individual modules.

I think for full clarity, the Dependencies page should also shown which individual modules are directly imported by the package.

(I also think Dependencies should list usage of global variables to reflect using of web standard and runtime specific APIs, but that's another issue)