How do I exclude ClientOptions from being generated?

[JamieHaywood-Lyka]

I've got multiple OpenAPI jsons that I want to parse into TypeScript types and then export from a root as a package. The problem I'm facing at the moment is:

Module './generated/auth' has already exported a member named 'ClientOptions'. Consider explicitly re-exporting to resolve the ambiguity.

Is there any way to exclude ClientOptions from being generated?

[dosubot[bot]]

Hi @JamieHaywood-Lyka! I'm Dosu and I’m helping the openapi-ts team.

There isn't a documented way to exclude ClientOptions from being generated—it's added by the client plugin and isn't controlled by schema filters or plugin options. The export ambiguity happens because each generated module exports its own ClientOptions type. You can work around this by disabling the generated index.ts file (output.indexFile: false) and importing only what you need from each module, or by explicitly re-exporting with aliases to avoid conflicts. If you don't need the client code at all, you can remove the client plugin from your config, but if you need the client, ClientOptions is part of its interface and will be generated for each spec reference.

To reply, just mention @dosu.

---

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

[mrlubos]

Not yet, but will add it