knit

Hi there. A few days ago, I posted a dev tool for Go to easily manage monorepos, called monogo (1). I hate the name, so I'm curious: do people have any good ideas for it? https://github.com/nicolasgere/monogo

It's surprising the go tooling doesn't have a more native way to do something like this already. Upstream issue: https://github.com/golang/go/issues/50745 Like, go already has test caching (so "only test stuff that changed" shouldn't be necessary, that should just happen), and code formatting and such is already quite fast... Overall, I feel like having another tool which parses my go source code is going to be slower than writing a Makefile to wrap: go list -f '{{.Dir}}' -m | xargs -L1 go test ./... which is all this tool doing really. Also, hilariously, the repo isn't go fmt'd [0], despite being a tool to go fmt your repo. That's really funny, but I don't think the go community is ready for that level of humor yet, maybe one day. [0]: https://github.com/nicolasgere/monogo/blob/2fb0b4985893e3397...

Hi there, I've been working sporadically over the last six months on a go monorepo tool (0 config it just use go workspace and go convention). It’s basically like TurboRepo but without the task runner. The tool builds a dependency graph between packages, allowing you to do things similar to what you can do in TurboRepo, like "only test the packages and the packages that depend on them, compared to the main branch," or "only install dependencies for Package A and its dependencies," etc. I use native go tool to get dependencies and create dependency graph between the package.Nothing crazy but I feel it could be useful.