Hi everyone! New to pants here - firstly I think it's an amazing tool, easy to use and quick setup. I was testing pants to move our (mostly Golang) services to monorepo. I am wondering how is people tackling the builds using a single go.mod in large projects. This is, if we have a monorepo with a few services and only a single go.mod, if I want to build a single service, it will download all the dependencies. Is something that support for go.work would help with?

cc @fast-nail-55400 who knows more about this than I…

go.work might help there since building a single module could refer to the go.work when it needs the dependency version. An unknown is whether Go tooling or Pants would need to inspect at least the modules to make sure they are valid etc. (And there could be other unknowns.)