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

# SvelteKit · Component state · HTTP polling

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

**Available recipes**

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

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

## Before you start

Start with an existing SvelteKit 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: `vite.config.ts`**

```ts
import { sveltekit } from "@sveltejs/kit/vite";
import { spinetab } from "spinetab/vite";
import { defineConfig } from "vite";

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

## 3\. Connect and render

Save these files together in `src/lib/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: `src/lib/recipe/live.ts`**

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

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

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

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

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

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

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

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

## 4\. Mount the view

**File: `src/routes/queue/+page.svelte`**

```svelte
<script lang="ts">
import Recipe from "../../lib/recipe/Recipe.svelte";
</script>
<main><Recipe /></main>
```

Keep your existing SvelteKit deployment adapter. Component lifecycle keeps live work out of server rendering; do not disable SSR or subscribe in a server load function.

## 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)
