#It seems related to having a `go.work`.
1 messages · Page 1 of 1 (latest)
I've also noticed this, if your go.work is malformed or no longer valid in any way, the way it manifests itself with errors in the dagger cli is pretty confusing. I see a lot of errors similar to this as I'm moving things around in my repo