Over time I expect there will be increasingly widespread adoption of tools.deps for expressing a library's dependencies, as well as increasing use of Leiningen/tools.deps integrations (such as lein-tools-deps) to minimise duplicated information.
It would be fantastic if lein-ancient was able to read tools.deps dependencies, and report out of date dependencies from that information, as well as from the Leiningen-native :dependencies vectors in project.clj files.
Over time I expect there will be increasingly widespread adoption of tools.deps for expressing a library's dependencies, as well as increasing use of Leiningen/tools.deps integrations (such as
lein-tools-deps
) to minimise duplicated information.It would be fantastic if
lein-ancient
was able to read tools.deps dependencies, and report out of date dependencies from that information, as well as from the Leiningen-native:dependencies
vectors inproject.clj
files.