Chris Thomas

> Originally, I wanted to support both type and interface but after talking with some of my peers and seeing how much they got lost between interface & dagger interface...

> If `interface` can be use to describe a dagger object, what's left to define a dagger interface? I don't really know enough about a "dagger interface" to be of...

If you are just using javascript, then you definitely won't access to the types. For this stuff it will all need to be with the compiler api. There is also...

That would also simplify the 'do we use `type` or `interface` for `dag.Interface`' question. As long as you can simplify the type, it doesn't matter which one is used. There...

> ⚠️ It seems yarn v4, and specially corepack with yarn v4 isn't working well with Dagger, I'm writing tests for everything except yarn v4 and may handle this later....

> It doesn't resolve dependencies correctly and output that `there's no type Container` in the basic quickstart example. > I'm super confused about that and think it might be because...

> Okay, I'll take care of that in a follow up PR then, supporting yarn v4 is something different thant the package manager configuration It's not really a `yarn-v4` thing....

> That's strange it's only failing with yarn v4 then? Other package manager works fine So `pnpm` isolates its dependencies, so that may not be an issue, but I'm pretty...

I know it will pick up the other lock file if it's at the root. Wasn't sure if it was going to pick it up from another folder. Yarn patches...

Does the sdk get installed separately from the module? That could be causing these issues since the dependencies would potentially change when the module is added. Also since there isn't...