-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Open
Labels
FeatureRequestIssues asking for a new feature that does not need a proposal.Issues asking for a new feature that does not need a proposal.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.UXIssues that involve UXD/UXR inputIssues that involve UXD/UXR inputpkgsite
Milestone
Description
Thanks for the great work on go.dev
website!
A given package has a "Imports" and "Imported By" tab, which allows you to get a sense of the dependency graph for a single package.
I propose adding a similar feature for modules, such that it would gain a "Requires" and a "Required By" tab that similarly presents the following information:
- For the "Requires" tab, it shows the set of modules required by the latest version of this module.
- For example, the latest version of
github.com/golang/protobuf
depends on 3 other modules. I'd expect these to be readily displayed without needing to go to thego.mod
file.
- For example, the latest version of
- For the "Required By" tab, it shows the set of modules at their latest version that requires this module.
- For example, the
github.com/golang/protobuf
module is required by 8577 modules. I'd like to see this number and get a brief sample of some of these modules. - It'd be additionally be useful if the "Required By" tab could show the dependencies on specific versions of this module. For example, I'd like to easily see statistics similar to the following:
- 1435x (16.7%) at v1.4
- 6199x (72.3%) at v1.3
- 721x (8.4%) at v1.2
- 77x (0.9%) at v1.1
- 45x (0.5%) at v1.0
- 100x (1.2%) at v0.0
- For example, the
At the present moment, I obtain such information through a series of expensive queries on the module proxy.
icholy, CAFxX and johnaoss
Metadata
Metadata
Assignees
Labels
FeatureRequestIssues asking for a new feature that does not need a proposal.Issues asking for a new feature that does not need a proposal.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.UXIssues that involve UXD/UXR inputIssues that involve UXD/UXR inputpkgsite