cli does not work on node 18

[lcdss]

Description

When trying to generate a client using node 18 the cli seems to no be executed. Absolutely no output is shown even with debug enabled. Running it with node 20 works correctly.

Reproducible example or configuration

mise exec node@18 -- npx @hey-api/openapi-ts --input https://petstore3.swagger.io/api/v3/openapi.json --output src/client-test -d

OpenAPI specification (optional)

No response

System information (optional)

No response

[dosubot]

According to the official documentation, Node.js 18 is supported and there are no known issues or special instructions for running the CLI on Node 18—it's expected to work the same as on Node 20 reference. Since you're seeing no output at all, even with debug enabled, this could be an environment-specific issue or related to how dependencies resolve under Node 18.

You could try: running with NODE_OPTIONS=--trace-warnings to see if any suppressed errors appear, checking if a global vs. local install changes the behavior, or running the CLI directly (not via npx) if possible. Also, check for any incompatible dependencies in your environment. If the problem persists, gathering more diagnostic info (like running with strace) might help pinpoint where it fails.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[lcdss]

@dosu Even with NODE_OPTIONS=--trace-warnings there's no output.

NODE_OPTIONS=--trace-warnings mise exec node@18 -- npx @hey-api/openapi-ts --input https://petstore3.swagger.io/api/v3/openapi.json --output src/client-test -d

[dosubot]

Node.js 18 is officially supported and there are no documented issues or special instructions for running the CLI on this version reference. Since you’re seeing a completely silent failure, here are some next steps that might help isolate the problem:

• Try running the CLI directly (not via npx) under Node 18 to rule out npx-specific issues.
• Test with a different Node 18 patch/minor version in case there’s a regression or compatibility difference.
• Run with alternative debug flags like --verbose or in a different shell/environment.
• Check for any logs, error files, or core dumps generated after running the CLI.
• Use a process tracing tool (like strace or dtruss) to see where the CLI process exits.
• Share details about your Node 18 environment (OS, shell, package manager versions) to help narrow down environmental factors.

If none of these reveal anything, using Node 20 as a temporary workaround is the safest path while investigating further.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[mrlubos]

@lcdss Is this a regression?

[mikavilpas]

Looks like @hey-api/openapi-ts 0.85.0 did not work for me on node 18.20.8, but 0.84.0 does

[lcdss]

@lcdss Is this a regression?

I can't say that as I just started trying out openapi-ts in a legacy app. Even typescript was in the v4 range and had to upgrade.

[mrlubos]

@lcdss Oof. Out of curiosity, why did you choose Hey API for your legacy project?

[lcdss]

@lcdss Oof. Out of curiosity, why did you choose Hey API for your legacy project?

Just because I'm using oRPC in the internal APIs and it has an integration with Hey API, so I decided to test it out.

[mrlubos]

@lcdss can you check if this preview build would run on Node 18 for you? #2731 (comment)