---
title: "Nuxt · Component state · HTTP polling"
url: "https://spinetab.com/docs/recipes/nuxt/direct/polling/"
description: "HTTP polling with Component state in Nuxt: dependencies, configuration, component and cleanup."
---

# Nuxt · Component state · HTTP polling

Render a live feed with your framework's component binding.

**Available recipes**

- [Nuxt · Component state · HTTP polling](https://spinetab.com/docs/recipes/nuxt/direct/polling.md)
- [Nuxt · Component state · Server-sent events](https://spinetab.com/docs/recipes/nuxt/direct/sse.md)
- [Nuxt · Component state · WebSocket](https://spinetab.com/docs/recipes/nuxt/direct/websocket.md)
- [Nuxt · Component state · Fetch stream](https://spinetab.com/docs/recipes/nuxt/direct/stream.md)
- [Nuxt · Component state · GraphQL over WebSocket](https://spinetab.com/docs/recipes/nuxt/direct/graphql-ws.md)
- [Nuxt · Component state · GraphQL over SSE](https://spinetab.com/docs/recipes/nuxt/direct/graphql-sse.md)
- [Nuxt · Component state · Socket.IO](https://spinetab.com/docs/recipes/nuxt/direct/socket-io.md)

HTTP polling · [Nuxt](https://spinetab.com/docs/setup/nuxt.md)

## Before you start

Start with an existing Nuxt app. Keep its renderer, routes and plugins. These files add one live view; Spinetab does not create your API.

Your endpoint supplies complete `{ "open": 12 }` values: JSON from GET /api/queue, read every five seconds by default.

The examples use same-origin URLs and declare `anonymous: true`: no token is supplied, although cookies still flow. For a separate API origin, use its URL and configure CORS or your application's proxy. For private data, add [credentials and user scopes](https://spinetab.com/docs/concepts/credentials.md); never put a secret in these files.

## 1\. Install

```sh
pnpm add spinetab
```

Keep your framework's existing dependencies. See [compatible versions](https://spinetab.com/docs/compatibility.md) if upgrading an older app.

## 2\. Configure your app

Merge this addition into your configuration; preserve existing plugins and options. Restart the dev server afterwards. The plugin bundles the worker and discovers the adapters imported below.

**File: `nuxt.config.ts`**

```ts
import { defineNuxtConfig } from "nuxt/config";

export default defineNuxtConfig({ modules: ["spinetab/nuxt"] });
```

## 3\. Connect and render

Save these files together in `app/components/recipe/`.

`reconcile: "latest"` fits this full-state contract: the next complete event restores the displayed value after a gap. Use a [refresh/merge policy](https://spinetab.com/docs/concepts/continuity.md) for deltas or partial GraphQL results. Reconnecting alone does not reconstruct missed state.

**File: `app/components/recipe/live.ts`**

```ts
import { createSpinetab } from "spinetab";

export const spinetab = createSpinetab({ anonymous: true });
```

**File: `app/components/recipe/queue-types.ts`**

```ts
export type Queue = { open: number };
export type QueueView = { open?: number; problem?: string };
```

**File: `app/components/recipe/source.ts`**

```ts
import { polling } from "spinetab/polling";
import type { Queue, QueueView } from "./queue-types";

export const queueSource = polling<Queue>("/api/queue");
export const selectQueue = (queue: Queue): QueueView => queue;
```

**File: `app/components/recipe/Recipe.vue`**

```vue
<script setup lang="ts">
import { bindClient } from "spinetab/vue";
import { spinetab } from "./live";
import { queueSource, selectQueue } from "./source";

const { useLive } = bindClient(spinetab);
const { data, error } = useLive(queueSource, {
	map: selectQueue,
	reconcile: "latest",
});
</script>

<template>
	<p v-if="error || data?.problem" role="alert">
		{{ error?.message ?? data?.problem }}
	</p>
	<p v-else-if="data?.open === undefined" role="status">Loading queue…</p>
	<p v-else><output>{{ data.open }}</output> open</p>
</template>
```

## 4\. Mount the view

**File: `app/pages/queue.vue`**

```vue
<script setup lang="ts">
import Recipe from "../components/recipe/Recipe.vue";
</script>
<template>
	<main><Recipe /></main>
</template>
```

Your existing `app/app.vue` must render `<NuxtPage />`. Work starts on browser mount; no ClientOnly wrapper is needed. KeepAlive retains subscriptions until the component is disposed.

## Check the result

Open /queue in two tabs of the same browser profile. Both should show advancing queue values. Matching subscriptions share upstream work when SharedWorker is available; fallback runs independently in each tab. Remove one view and the other should keep updating. Removing the last view releases its subscription; connection closure can follow the adapter's idle delay.

[API options and advanced recovery](https://spinetab.com/docs/transports/polling.md) · [Authentication](https://spinetab.com/docs/concepts/credentials.md)
