KV

Read and write key-value data through one portable runtime handle across Vite, Nitro, and Nuxt.

@vitehub/kv gives Vite, Nitro, and Nuxt apps one kv handle for application state that fits a key-value shape.

Use KV when route code needs to read or write small JSON-serializable values without carrying provider-specific SDK calls through the app. The provider choice stays in config. Runtime code keeps the same kv.get(), kv.set(), and kv.del() calls.

import { kv } from '@vitehub/kv'

export default defineEventHandler(async () => {
  await kv.set('settings', {
    theme: 'system',
    onboardingComplete: true,
  })

  return { ok: true }
})

import { kv } from '@vitehub/kv'

export default defineEventHandler(async () => {
  return {
    settings: await kv.get('settings'),
  }
})

{
  "settings": {
    "theme": "system",
    "onboardingComplete": true
  }
}

What KV Solves

Provider storage SDKs are useful, but they couple route code to deployment infrastructure.

KV puts the provider behind the Nitro storage mount:

Portable runtime calls

Use the same kv handle for local development, Cloudflare KV, and Upstash-backed Vercel deployments.

Config-based routing

Pick fs-lite, cloudflare-kv-binding, or upstash in config or let ViteHub infer the driver.

Nitro storage backing

Mount the active driver as Nitro storage at kv, then expose a small typed wrapper.

Secret-safe Upstash setup

Keep Upstash credentials in runtime environment variables instead of serializing them into build output.

One Portable Flow

The same shape works across supported frameworks:

Install @vitehub/kv.
Register hubKv(), @vitehub/kv/nitro, or @vitehub/kv/nuxt.
Choose a driver or let ViteHub resolve one.
Import kv from @vitehub/kv in server/runtime code.
Read and write values with get, set, has, del, keys, and clear.

Provider-specific setup belongs in framework config and deployment environment variables. Application call sites should stay provider-neutral unless you intentionally pass driver-specific options.

Driver Routing

ViteHub resolves KV config in this order:

Priority	Signal	Resolved driver
1	Explicit `kv.driver`	The configured driver
2	`KV_REST_API_URL` and `KV_REST_API_TOKEN`	`upstash`
3	Vercel hosting	`upstash`
4	Cloudflare hosting	`cloudflare-kv-binding`
5	Everything else	`fs-lite`