A powerful Nuxt module for integrating TanStack Query (formerly Vue Query) into your Nuxt application. Provides robust server state management with intelligent caching, background updates, and seamless data synchronization.
- ⚙️ Zero-configuration integration
- 💪 Full TypeScript support with Vue Query configuration
- 🏆 Advanced
QueryClientsetup with custom handlers via hooks - 🤖 Configurable auto-imports for Vue Query composables
- 🧩 Nuxt DevTools integration for debugging and inspection
You can add the module via the Nuxt CLI:
npx nuxi module add @peterbud/nuxt-queryor via npm:
npm install @peterbud/nuxt-queryTo configure Nuxt Query, update your nuxt.config.ts specifying the options you want for Vue Query:
// nuxt.config.ts
export default defineNuxtConfig({
modules: ['@peterbud/nuxt-query'],
nuxtQuery: {
/**
* Specify which Vue Query composables to auto-import
* Default: `false`, set to `true` to auto-import all Vue Query composables
*/
autoImports: ['useQuery', 'useMutation'],
// Enable/disable Nuxt DevTools integration (default: true)
devtools: true,
/**
* These are the same options as the QueryClient
* from @tanstack/vue-query, which will be passed
* to the QueryClient constructor
* More details: https://tanstack.com/query/v5/docs/reference/QueryClient
*/
queryClientOptions: {
defaultOptions: {
queries: {
// for example disable refetching on window focus
refetchOnWindowFocus: false,
// or change the default refetch interval
refetchInterval: 5000,
},
},
},
},
})Then, in your component, you can define and run queries with the useQuery composable (auto-imported):
// app.vue
<script setup>
const getPosts = async () => {
await new Promise(resolve => setTimeout(resolve, 2000))
return await $fetch('https://jsonplaceholder.typicode.com/posts')
}
const { isPending, isFetching, isError, data, error } = useQuery({
queryKey: ['posts'],
queryFn: getPosts,
})
</script>That's it! You can now use Nuxt Query in your Nuxt app ✨
Nuxt Query provides a hook that you can use in your application if you need a more complex setup for TanStack Query, such as a custom query client with centralized onSuccess or onError handlers, which would not be possible to configure with the options available in the nuxt.config.ts.
The hook is called nuxt-query:configure and you can use it in a plugin to return a custom QueryClient object in the following way:
// plugins/nuxt-query.ts
import { QueryClient, QueryCache } from '@tanstack/vue-query'
export default defineNuxtPlugin({
enforce: 'pre',
setup(nuxtApp) {
nuxtApp.hook('nuxt-query:configure', (getPluginOptions) => {
const clientOptions = useRuntimeConfig().public.nuxtQuery?.queryClientOptions || {}
const queryClient = new QueryClient({
...clientOptions,
queryCache: new QueryCache({
onSuccess: (data: unknown) => console.log('onSuccess', { data }),
}),
})
// return the plugin options which will be used
// by the module at startup
getPluginOptions(queryClient)
})
},
})Await server queries with onServerPrefetch(suspense) or await queryClient.prefetchQuery(). The module dehydrates the query cache after rendering and hydrates it in the browser before components mount. Queries that finish after rendering are not guaranteed to be included.
Each server request gets its own QueryClient. Custom clients supplied through nuxt-query:configure must also be created per request.
Nuxt handles payload transport and prefetching. For routes with extracted payloads, the module also hydrates the destination cache on successful navigation. With experimental.payloadExtraction:
'client': initial data is inline; navigation uses extracted payloads.true: both initial visits and navigation use extracted payloads.false: initial SSR data is inline; navigation fetches queries normally.
TanStack handles cache merging and freshness: older payload data does not overwrite newer browser data, and stale queries can refetch. Set staleTime as needed; it is independent of Nitro's SWR/ISR response lifetime.
Use defaultOptions.dehydrate on a custom QueryClient to filter or transform dehydrated data. Nuxt handles payload serialization; the module does not make arbitrary classes or functions serializable.
Only cache public routes with shared SWR/ISR. Per-request QueryClients do not protect user-specific data in cached HTML or payloads. Dehydration filters exclude data from the payload, not from rendered HTML.
Nuxt Query integrates with Nuxt DevTools to provide a dedicated tab for Vue Query, where you can inspect the state of your queries, view their cache, and properties, initiate refetch or remove certain queries and more.
Also, you can inspect your mutation cache using the same DevTools in a convenient way.
Local development
# Install dependencies
npm install
# Generate type stubs
npm run dev:prepare
# Develop with the playground
npm run dev:client
# Build the playground
npm run dev:build
# Run ESLint
npm run lint
# Install Chromium for the Nuxt browser tests
pnpm exec playwright-core install chromium
# Run Vitest
npm run test
npm run test:watch
# Build the module
npm run build
# Release new version
npm run releaseIf you want to report a bug, please make sure you have a minimal reproduction of the issue. You can use the minimal example to create a reproduction.

