Options

Option	Type	Default	Description
output	Output	{ path: 'hooks', barrel: { type: 'named' } }	Where the generated composables are written and exported
group	Group	—	Split output into per-tag or per-path folders
client	'axios' | 'fetch'	—	Which registered client plugin the composables call
infinite	Partial<Infinite> | false	false	Add useInfiniteQuery composables for paginated reads
query	Partial<Query> | false	{ methods: ['GET'], … }	Configure or disable query composables
queryKey	(props) => Array<unknown>	built-in	Build the queryKey for each query composable
mutation	Partial<Mutation> | false	{ methods: ['POST', …], … }	Configure or disable mutation composables
mutationKey	(props) => Array<unknown>	built-in	Build the mutationKey for each mutation composable
hooks	boolean	false	Emit use* composables on top of the factory helpers
include	Array<Include>	—	Keep only operations that match
exclude	Array<Exclude>	—	Skip operations that match
override	Array<Override>	—	Apply different options per pattern
resolver	Partial<ResolverVueQuery>	—	Customize generated names and file paths
macros	Array<Macro>	—	Rewrite AST nodes before printing

output

Where the generated composables are written and how they are exported.

Type:	Output
Default:	{ path: 'hooks', barrel: { type: 'named' } }

output.path

Folder where the plugin writes its files. It is resolved against the global output.path on defineConfig. To write everything to one file instead, set output.mode: 'file' and give path a file name with its extension, such as 'hooks.ts'.

Type:	string
Default:	'hooks'

TIP

output.path sets where files go, output.mode sets how many. Use 'directory' (the default) for one file per operation, optionally grouped into subdirectories with the group option. Use 'file' to write everything into a single file.

output.mode

How the plugin consolidates its generated code into files.

• 'directory' (default) writes one file per operation or schema under output.path.
• 'file' writes everything into a single file. The output.path must include the file extension (for example 'hooks.ts').

Type:	'directory' | 'file'
Default:	'directory'

TIP

Pair 'directory' with the group option to organize output into per-tag or per-path subdirectories. mode: 'file' forbids group. A single-file output has nothing to group, and combining them stops the build with a KUBB_INVALID_PLUGIN_OPTIONS error.

output.barrel

Controls how the generated index.ts (barrel) file re-exports the plugin's output.

• { type: 'named' } re-exports each symbol by name. Best for tree-shaking and explicit imports.
• { type: 'all' } uses export *. Smaller barrel file, but exports everything.
• { nested: true } creates a barrel in every subdirectory, so callers can import from any depth.
• false skips the barrel entirely. The plugin's files are also excluded from the root index.ts.

Type:	{ type: 'named' | 'all', nested?: boolean } | false
Default:	{ type: 'named' }

TIP

Pick 'named' when consumers care about which symbols they import (better tree-shaking, friendlier auto-import). Pick 'all' when the file count is small and you want a one-line barrel.

'named' (default)

// src/gen/hooks/index.ts
export { getPetsQueryKey, getPetsQueryOptions } from './useGetPets'
export { createPetMutationKey } from './useCreatePet'

'all'

// src/gen/hooks/index.ts
export * from './useGetPets'
export * from './useCreatePet'

nested

src/gen/hooks/
├── index.ts          # re-exports ./pet and ./store
├── pet/
│   ├── index.ts      # re-exports getPetsQueryKey, getPetsQueryOptions, ...
│   └── useGetPets.ts
└── store/
    ├── index.ts
    └── useGetStoreById.ts

false

# No index.ts is generated for this plugin.
# Its files are also excluded from the root index.ts.

output.banner

Text added to the top of every generated file. Use it for license headers, lint disables, or a @ts-nocheck directive. Pass a string for a fixed banner, or a function that builds one from a BannerMeta object. The meta carries the document info (title, description, version, baseURL) plus the per-file context filePath, baseName, isBarrel, and isAggregation, so a directive such as 'use server' can skip barrel files.

Type:	string | ((meta: BannerMeta) => string)

A static banner: '/* eslint-disable */\n// @ts-nocheck' lands at the top of each generated file.

A function banner builds the text from the meta, such as banner: (meta) => \// Source: ${meta.filePath}``.

output.footer

Text added to the bottom of every generated file. It works like banner but for closing comments, such as re-enabling a lint rule. Pass a string or a function that receives the same BannerMeta and returns the text. Pair banner: '/* eslint-disable */' with footer: '/* eslint-enable */' to scope a lint disable to the generated file.

Type:	string | ((meta: BannerMeta) => string)

group

Splits generated files into subfolders by the operation's tag or URL path. Each group gets its own directory under {output.path}/{groupName}/. Without group, every file lands directly in output.path.

Type:	Group

TIP

Use group to mirror your API's domain structure (pet, store, user) in the generated code. Combine it with output.barrel: { type: 'named', nested: true } to get per-tag barrel files.

group only applies to output.mode: 'directory' (the default). It is not valid with output.mode: 'file', since a single-file output has no grouping concept.

With group: { type: 'tag' }, the generator emits one folder per tag, named after the camelCased tag:

Resulting tree

src/gen/hooks/
├── pet/
│   ├── useCreatePet.ts
│   └── useGetPets.ts
└── store/
    ├── useCreateStore.ts
    └── useGetStoreById.ts

Pass group.name to customize the folder name. For example, a name function that appends Hooks to the group keeps a petHooks/ layout.

group.type

Property used to assign each operation to a group. Required whenever group is set.

• 'tag' uses the operation's first tag.
• 'path' uses the first segment of the operation's URL, such as pet for /pet/{petId}.

An operation with no tag goes in the default group.

Type:	'tag' | 'path'

group.name

Function that turns a group key (the operation's first tag) into a folder or identifier name. The result is used as both the subdirectory name under output.path and as a suffix when naming aggregate files.

Type:	(context: { group: string }) => string
Default:	({ group }) => camelCase(group)

For type: 'path' groups, the default uses the first URL segment as-is instead of camelCasing.

client

Selects which registered client plugin the generated composables call. Set 'axios' to use @kubb/plugin-axios or 'fetch' to use @kubb/plugin-fetch. When omitted, the plugin auto-detects the single client plugin in the config, so you only need this option to disambiguate when several client plugins are registered. A client plugin must be registered, since the composables call its functions.

Type:	'axios' | 'fetch'

infinite

Adds infinite-query output for cursor- or page-based pagination. Pass an object to configure how the cursor is read from the response. Pass false (default) to skip it. Set the hooks option to wrap the output in useInfiniteQuery.

Type:	Partial<Infinite> | false
Default:	false

IMPORTANT

Infinite output is emitted per operation only when the operation declares a query parameter whose name matches infinite.queryParam (default 'id'). Operations without that parameter keep their regular query output.

With infinite: false (the default), a GET /pets operation generates getPetsQueryOptions. Setting infinite: {} adds an extra getPetsInfiniteQueryOptions factory that reads the cursor from the response:

infinite: false (default)

export function getPetsQueryOptions(/* ... */) {
  return queryOptions({ queryKey, queryFn })
}

infinite: {}

export function getPetsInfiniteQueryOptions(/* ... */) {
  return infiniteQueryOptions({ queryKey, queryFn, initialPageParam, getNextPageParam })
}

Which factory you reach for depends on the value:

infinite: false (default)

import { getPetsQueryOptions } from './src/gen/hooks/useGetPets'

const { data } = useQuery(getPetsQueryOptions())

infinite: {}

import { getPetsInfiniteQueryOptions } from './src/gen/hooks/useGetPetsInfinite'

const { data, fetchNextPage, hasNextPage } = useInfiniteQuery(getPetsInfiniteQueryOptions())
// data.pages holds each fetched page

infinite.queryParam

Name of the query parameter that holds the page cursor.

Type:	string
Default:	'id'

infinite.initialPageParam

Initial value for pageParam on the first fetch.

Type:	unknown
Default:	0

infinite.nextParam

Path to the next-page cursor on the response. Supports dot notation ('pagination.next.id') or array form (['pagination', 'next', 'id']).

Type:	string | string[] | null
Default:	null

infinite.previousParam

Path to the previous-page cursor on the response. Supports dot notation ('pagination.prev.id') or array form (['pagination', 'prev', 'id']).

Type:	string | string[] | null
Default:	null

query

Decides which operations are treated as queries and how their output is built. The plugin generates a queryOptions factory for each matching operation by default. Pass false to skip query generation entirely. Set the hooks option to also emit the useQuery wrapper.

Type:	Partial<Query> | false
Default:	{ methods: ['GET'], importPath: '@tanstack/vue-query' }

query.methods

HTTP methods treated as queries. Operations using one of these methods generate a queryOptions factory instead of a mutation. Add a method such as 'head' only when your API uses it for cache-friendly reads.

Type:	Array<string>
Default:	['get']

query.importPath

Module specifier used in the import { queryOptions } from '...' statement at the top of every generated composable file. Point it at your own re-export of TanStack Query, such as a wrapper that injects a default queryClient.

Type:	string
Default:	'@tanstack/vue-query'

queryKey

Builds the queryKey for each generated query composable. Use it to add a version namespace, key off the operation ID, or match an existing queryClient.invalidateQueries strategy. The callback receives the operation node and the active casing, and returns the array of values that make up the key. When unset, it defaults to Kubb's built-in key builder (queryKeyTransformer).

Type:	(props: { node: OperationNode; casing }) => Array<unknown>
Default:	built-in

WARNING

String values are inlined verbatim into generated code. Wrap any literal string in JSON.stringify(...).

Keying off the operation ID changes the generated queryKey helper:

queryKey builder

queryKey: ({ node }) => [JSON.stringify(node.operationId)]

Generated output

export const getUserByNameQueryKey = () => ['getUserByName'] as const

You call the composable the same way, but the key shape changes how you invalidate it:

import { useQueryClient } from '@tanstack/vue-query'
import { getUserByNameQueryKey } from './src/gen/hooks/useGetUserByName'

const queryClient = useQueryClient()
queryClient.invalidateQueries({ queryKey: getUserByNameQueryKey() })

mutation

Decides which operations are treated as mutations and how their output is built. The plugin generates a mutationKey helper for each matching operation by default. Pass false to skip mutation generation. Set the hooks option to also emit the useMutation wrapper.

Type:	Partial<Mutation> | false
Default:	{ methods: ['POST', 'PUT', 'PATCH', 'DELETE'], importPath: '@tanstack/vue-query' }

mutation.methods

HTTP methods treated as mutations. Operations using one of these methods generate mutation output instead of a query. Narrow the list if your API uses one of these methods for reads.

Type:	Array<string>
Default:	['post', 'put', 'patch', 'delete']

mutation.importPath

Module specifier used in the import { useMutation } from '...' statement at the top of every generated composable file, emitted when the hooks option is set. Point it at your own wrapper.

Type:	string
Default:	'@tanstack/vue-query'

mutationKey

Builds the mutationKey for each mutation composable. Use it when you batch invalidations or read mutation state with useMutationState. The callback receives the same { node, casing } props as queryKey. When unset, it defaults to Kubb's built-in key builder (mutationKeyTransformer).

Type:	(props: { node: OperationNode; casing }) => Array<unknown>
Default:	built-in

WARNING

String values are inlined verbatim into generated code. Wrap any literal string in JSON.stringify(...).

hooks

Controls whether use* composable functions are emitted. When set to false (the default), the plugin writes only the factory helpers: queryOptions, queryKey, and mutationKey. Set to true to also generate useQuery, useInfiniteQuery, and useMutation composables.

The factory helpers work with any TanStack Query adapter. You can pass the same queryOptions object to prefetchQuery, setQueryData, and router loaders without wrapping it in a composable.

Type:	boolean
Default:	false

hooks: false (default)

// only factories, no use* composables
import { getPetsQueryOptions } from './src/gen/hooks/useGetPets'

const options = getPetsQueryOptions()
const data = await queryClient.fetchQuery(options)

hooks: true

// factories plus the composable
import { useGetPets } from './src/gen/hooks/useGetPets'

const { data, isLoading } = useGetPets()

include

Generates only the operations that match at least one entry in the list. Everything else is skipped. Each entry filters by one of:

• tag: the operation's first tag in the OpenAPI spec.
• operationId: the operation's operationId.
• path: the URL path, such as '/pet/{petId}'.
• method: the HTTP method, such as 'GET' or 'POST'.
• contentType: the request or response media type, such as 'application/json'.
• schemaName: the component schema name under #/components/schemas.

pattern accepts either a string (exact match) or a RegExp for fuzzy matches.

Type:	Array<Include>

Type definition

export type Include = {
  type: 'tag' | 'operationId' | 'path' | 'method' | 'contentType' | 'schemaName'
  pattern: string | RegExp
}

Pass include: [{ type: 'tag', pattern: 'pet' }] to keep only the pet tag. Stack entries to narrow further, such as { type: 'method', pattern: 'GET' } with { type: 'path', pattern: /^\/pet/ } for GET operations under /pet.

exclude

Skips any operation that matches at least one entry in the list. It is the opposite of include. Entries use the same type (tag, operationId, path, method, contentType, schemaName) and pattern (string or RegExp). When both are set, exclude wins.

Type:	Array<Exclude>

Type definition

export type Exclude = {
  type: 'tag' | 'operationId' | 'path' | 'method' | 'contentType' | 'schemaName'
  pattern: string | RegExp
}

Pass exclude: [{ type: 'tag', pattern: 'store' }] to drop the store tag, or stack { type: 'operationId', pattern: 'deletePet' } with { type: 'method', pattern: 'DELETE' } to skip one operation and every DELETE.

override

Applies different plugin options to operations that match a pattern. Use it for the few endpoints that need special treatment. Each entry takes the same type and pattern as include and exclude, plus an options object. That object accepts any plugin option except override, so rules cannot nest. Entries run top to bottom. The first match merges onto the plugin defaults, and later entries do not stack.

Type:	Array<Override>

Type definition

export type Override = {
  type: 'tag' | 'operationId' | 'path' | 'method' | 'contentType' | 'schemaName'
  pattern: string | RegExp
  options: Omit<Partial<Options>, 'override'>
}

For example, override: [{ type: 'tag', pattern: 'user', options: { mutation: false } }] skips mutation composables for the user tag while the rest of the spec keeps the plugin default.

resolver

Changes how the plugin names generated composables and files. Use it to add a prefix or suffix, or to swap the casing, without forking the plugin. Override only the methods you want to change, since anything you omit keeps its default behavior. Inside a method, this is the full resolver, so you can call this.default(name, 'function') to reuse the built-in name.

Type:	Partial<ResolverVueQuery> & ThisType<ResolverVueQuery>

TIP

Use resolver for naming and file-location tweaks. To change the AST nodes themselves, such as stripping descriptions, use macros instead.

The default resolver is resolverVueQuery.

macros

Rewrites AST nodes before they are printed to source. Use it to rename operation IDs, drop descriptions, or change schema metadata without forking the generator. Each macro callback (such as schema or operation) receives the node and a context object. Return a new node to replace it, or undefined to leave it as is. Macros run in order, so a later one sees the output of an earlier one.

Type:	Array<Macro>

TIP

Use macros to rewrite node properties before printing. To change the names of generated symbols and files, use resolver instead.