---
title: "Vite · React · SWR · HTTP polling"
url: "https://spinetab.com/docs/recipes/vite-react/swr/polling/"
description: "HTTP polling with SWR in Vite · React: dependencies, configuration, component and cleanup."
---

# Vite · React · SWR · HTTP polling

Use shared subscriptions in a React app with SWR.

**Available recipes**

- [Vite · React · SWR · HTTP polling](https://spinetab.com/docs/recipes/vite-react/swr/polling.md)
- [Vite · React · SWR · Server-sent events](https://spinetab.com/docs/recipes/vite-react/swr/sse.md)
- [Vite · React · SWR · WebSocket](https://spinetab.com/docs/recipes/vite-react/swr/websocket.md)
- [Vite · React · SWR · Fetch stream](https://spinetab.com/docs/recipes/vite-react/swr/stream.md)
- [Vite · React · SWR · GraphQL over WebSocket](https://spinetab.com/docs/recipes/vite-react/swr/graphql-ws.md)
- [Vite · React · SWR · GraphQL over SSE](https://spinetab.com/docs/recipes/vite-react/swr/graphql-sse.md)
- [Vite · React · SWR · Socket.IO](https://spinetab.com/docs/recipes/vite-react/swr/socket-io.md)

HTTP polling · [Vite · React](https://spinetab.com/docs/setup/vite.md)

## Before you start

Start with an existing Vite · React 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 swr@^2.5.1
```

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: `vite.config.ts`**

```ts
import react from "@vitejs/plugin-react";
import { spinetab } from "spinetab/vite";
import { defineConfig } from "vite";

export default defineConfig({ plugins: [react(), spinetab()] });
```

## 3\. Connect and render

Save these files together in `src/recipe/`.

SWR uses its default cache. The constant `queue` key always returns the same source; if the endpoint varies, derive it from that key. With SWR 2.5.1 and React 19.3, avoid nesting a custom cache provider inside StrictMode; see [the upstream restriction](https://spinetab.com/docs/integrations/swr.md#use-it-in-your-app).

`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: `src/recipe/live.ts`**

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

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

**File: `src/recipe/queue-types.ts`**

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

**File: `src/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: `src/recipe/Recipe.tsx`**

```tsx
import { swrSubscription } from "spinetab/swr";
import useSWRSubscription from "swr/subscription";
import { spinetab } from "./live";
import { queueSource, selectQueue } from "./source";

const subscribe = swrSubscription(spinetab, (_key: "queue") => queueSource, {
	map: selectQueue,
	reconcile: "latest",
});

export default function Recipe() {
	const { data, error } = useSWRSubscription("queue", subscribe);
	if (error || data?.problem)
		return <p role="alert">{error?.message ?? data?.problem}</p>;
	if (data?.open === undefined) return <p role="status">Loading queue…</p>;
	return (
		<p>
			<output>{data.open}</output> open
		</p>
	);
}
```

## 4\. Mount the view

**File: `src/App.tsx`**

```tsx
import Recipe from "./recipe/Recipe";
export default function App() {
	return <Recipe />;
}
```

Your existing entry point mounts App as usual. Keep its renderer plugin; no additional application provider is required beyond those shown.

## Check the result

Open the page 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/integrations/swr.md) · [Authentication](https://spinetab.com/docs/concepts/credentials.md)
