Jffarge
Jffarge
Currently, if an error occur, it's printed out but the exit code is still 0. We should trigger a more appropriate `process.exit(1)`.
If docker isn't running you get the following error: We should catch this error and display an appropriate message.
 As a follow up it would be good to modify this test case to be similar to the one in Go or Python...
To be more consistent with Go and Python SDKs, we should pass strings as arguments instead of object with the NodeJS query builder. ```typescript // BEFORE const node = await...
The Node.js SDK is currently returning the last part of the nested Graphql object result. We should directly return the appropriate primitives. Today: ```ts const source = client.host().workdir().id() console.log(source) //...
The test is currently skipped. It pass locally but failed with `./hack/make sdk:nodejs:test` Signed-off-by: jffarge
Our current ref docs need to be reviewed. Some outputs are not displayed in the good place. For instance Type aliases `FileID` is displayed here :https://docs.dagger.io/current/sdk/nodejs/reference/modules/api_client_gen A better place to...
### What is the issue? I'm trying to write a new file with the following script: ```typescript import Client, { connect } from "@dagger.io/dagger" connect(async (client: Client) => { const...
### What is the issue? The error occurs when I follow the section `export-the-build-directory` from the docs: https://docs.dagger.io/zenith/quickstart/853930/directories/#export-the-build-directory I'm getting an error when trying to check the Dagger version: ```...
When I initialize a new module with `dagger init` and I mistyped the `--sdk`, I'm getting the following error. ``` $ dagger init --name=my-module --sdk=typescrip Error: failed to generate code:...