Vasek - Tom C
Vasek - Tom C
Fixed by #10736, please reopen if there's anything missing to solve that issue.
> We do see typescript tests timing out (even just the SDK tests) - potentially some changes there could have caused this. @TomChv This should have been fixed with #7827
@shykes > Best DX: one package manager, one runtime, one way to organize your files. Probably customizable, but not infinitely so. Probably easier to learn, easier to develop, and faster....
> In terms of the package managers, it depends on how strict you want to be with where dagger modules live. If you go down the road of only supporting...
It seems this issue happens only sometime with no correlation between a specific setup and this issue, if anyone have this issue on every run, please provide a repro case...
@gerhard Did you hit this issue recently with v0.12? I didn't on my side and did not see the issue recently in the CI
I'm closing this issue since it seems this problem hasn't happen for couple of months. Please reopen it if it happen again.
> Currently the typescript sdk installs itself as a folder within the project and has its own package.json and lock file. This makes things a little tricky to work around...
> There are two unique parts. One is the SDK itself, and the other is the code-gen part. Those could be split up. Some libraries that rely heavily on code-gen,...
Related to that issue: https://github.com/dagger/dagger/pull/9531. If extended to module's client gen, this would use the published library :)