bcmills
commented
5 years ago In Go modules, the module is the unit of dependency. When you are using a proxy (slated to be enabled by default in Go 1.13), you will download only the go.mod files (and not the full source code) for unneeded dependencies in the module graph.
For registry-style APIs, I would recommend placing the service-specific implementations in a separate module from the registry package itself. Then the “conditional” aspect of the module graph is exactly: “which packages are in the package import graph?”.
dfang
mentalisttraceur
gopherbot
What version of Go are you using (
go version)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env)?go envOutputWhat did you do?
main.go
when you run
go mod graph, you can see so many dependencies,Output
What did you expect to see?
what if i only use postgres db, please don't install mssql, sqlite dependencies for me.
i'm not sure this feature calls, maybe conditional dependencies ?
this pattern is common in some library that as a provider .....
What did you see instead?
a huge dependencies tree
Extra information (FYI)
i was a ruby on rails developer, as my experience, package management in node.js is sucking, big node_modules, installed failed, unmet dependencies ...
however in ruby world, package management (bundler) is nearly perfect, maybe go mod designer can learn something from that