tanstack query vue TComposable / DefaultT not resolved

[9M6]

Description

TCompsable and DefaultT when generating tanstack vue queries not resolved correctly:

Reproducible example or configuration

import { defaultPlugins, defineConfig } from "@hey-api/openapi-ts";
import dotenv from "dotenv";

dotenv.config();

export default defineConfig({
  input: "http://localhost:9000/docs-json",
  output: {
    format: "prettier",
    lint: "eslint",
    path: "sdk",
  },
  plugins: [
    ...defaultPlugins,
    "zod",
    {
      enums: "typescript", // default
      name: "@hey-api/typescript",
    },
    {
      name: "@hey-api/client-nuxt",
      runtimeConfigPath: "./api.config.ts",
    },
    {
      asClass: true, // default
      name: "@hey-api/sdk",
    },
    {
      name: "@tanstack/vue-query",
      mutationOptions: true,
    },
  ],
});

OpenAPI specification (optional)

No response

System information (optional)

No response

[dosubot]

The official documentation for the TanStack Query plugin in @hey-api/openapi-ts shows support for Vue and describes generating query functions, keys, and mutation options, but does not mention TComposable or DefaultT types anywhere, nor does it provide troubleshooting steps for type resolution issues with these types reference.

This suggests TComposable and DefaultT may be internal or inferred types not documented or possibly related to type generation issues. Here are some steps you can take:

• Check the generated SDK/code for references to TComposable and DefaultT and see if they are missing imports or unresolved types.
• Make sure all dependencies (@tanstack/vue-query, @hey-api/openapi-ts, and their types) are installed and compatible.
• If the types are not present or documented, try isolating the issue by generating with a minimal OpenAPI spec or adjusting plugin options.
• Review your tsconfig.json for type resolution issues and search for naming mismatches.

If the problem persists, it may be a misconfiguration or a bug in the plugin. Since there are no known issues or discussions about these types in the documentation, inspecting the generated code and your dependency setup is the best next step.

To reply, just mention @dosu.

---

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

[mrlubos]

@9M6 can you create a StackBlitz example? It's not obvious from the screenshot what's the issue