Thinking about this again I could feel | Dagger | Page 1

Yeah the connection is not obvious. It's that when you load an extension, it by default will just include the project workdir, and by default that workdir is the directory tree under cloak.yaml.

The problem is that we need to make sure any go extensions' go.mod is included when it's loaded up (so it can be built). Same is true for nodejs w/ package.json.

Right now that all works because there is a go.mod in the root of the repo and that's where we are picking up cloak.yaml. But if we use a cloak.yaml in a subdir we'd need to make sure that a go.mod for the extensions still gets picked up.

I just realized another possible solution here is to just update all the tests to do the equivalent of running cloak do -p ... from the root of the repo. Actually we already do that for some tests, e.g. here: https://github.com/sipsma/dagger/blob/f81a1e158dff80b7bb3cf06fa5331c6a9256122f/core/integration/project_test.go#L17-L17

So maybe we just need to update the testutil to do that too

#Thinking about this again I could feel