Not integrated with the package catalog, but there's the package graph
visualizer:
https://docs.racket-lang.org/pkg-dep-draw/index.html
Vincent
On Mon, 21 Mar 2016 17:04:34 -0500,
Jack Firth wrote:
>
> It would be great if (opening words to many a pipe dream but
> nevertheless) the package catalog UI directly included information about
> what other packages are dependent on a package, at least for the
> purposes of package developers. This is useful information beyond
> backwards-compatibility concerns, as it makes it easy to track down the
> source code of clients to see how people are actually using your
> package. It's also a good indicator of how "core" a package is and how
> supported it is, fringe package X with zero clients could be completely
> broken and nobody would notice while commonly used package Y which a
> fifth of the catalog depends on can be relatively trusted.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-dev/4f015c2b-1bd2-4f1e-bca1-0e0782ecad32%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-dev/m2mvprfibp.wl-stamourv%40eecs.northwestern.edu.
For more options, visit https://groups.google.com/d/optout.
