Yes, thanks @near storm . I went through the quick start and then tried to replicate my current convoluted e2e test pipeline setup working with the TypeScript SDK.
I somehow got sidetracked with an example in the old non-module syntax connect( async (client: Client) => {} , then tried to dagger install a node module from the daggerverse and couldn't get it to appear on my client object. After some further research, I initialized a proper ts-module, reinstalled the node module and now it got actually installed into my dagger.json and sdk/ folder.
Fast forward, after defining a few containers for frontend, backend, database and playwright I struggled to get my source-directory mounted, as the host() method seems to have disappeared from the dag::Client object, even if it is still listed in the docs (https://docs.dagger.io/reference/typescript/classes/api_client_gen.Client). So how can I get a source directory into my dag.node.withSource(source: Directory) container?
This issue here https://github.com/dagger/dagger/issues/6955 mentions, that I should use a combination of my shiny new TS module together with an old-school non-module TS script, which does have access to the host container. If I add such a e2e-test.ts script to my dagger module folder, it will however have the same Client module without client.host(). And if I put the script into a separate folder with it's own package.json, tsconfig.json, then it won't have access to my module anymore.
Sorry for the long story, but I hope it helps to see where a developer starting today can get lost in the current state of docs, and where some hints or caveats would already help to steer the reader into the right direction.