ahh this is useful https://go.dev/doc/modules/managing-dependencies. the go culture doesn’t typically have large dependency graphs like Ruby or JS.

@lyse@lyse.isobeef.org What the actual fuck?! 😅 Man I’d better go through and do some “dependency cleanup” 🤦‍♂️ How da fuq is protobuf being pulled in again?! 🤔

I don’t get it 😢

$ go mod why github.com/golang/protobuf
# github.com/golang/protobuf
(main module does not need package github.com/golang/protobuf)

@lyse@lyse.isobeef.org What is go mod graph really showing? 🤔

Oh this is interesting…

$ go mod why -m github.com/golang/protobuf
# github.com/golang/protobuf
git.mills.io/yarnsocial/yarn/internal
git.mills.io/prologic/observe
github.com/prometheus/client_golang/prometheus
github.com/golang/protobuf/proto

@lyse@lyse.isobeef.org I don’t think so?

@lyse@lyse.isobeef.org Probably will. Y think the intention was to build UI / integration tests but that has never happened 😆

@lyse@lyse.isobeef.org I tend to agree with you, years gone back a long time ago, I remember how badly Selenium based testing sucked too 😅

@lyse@lyse.isobeef.org im talking like some JS projects i have seen with 1-2G node_modules dirs. though yarn is quite vast in its modules because it does a LOOOOOOT of stuff in the background.

how install gomodot? also.. @prologic@twtxt.net your domain has some pretty strong SEO mojo searching for install "gomodot" puts you on the google first page.