Cloudflare KV

Configure KV

Register the Nuxt module and set kv.driver to cloudflare-kv-binding:

export default defineNuxtConfig({
  modules: ['@vitehub/kv/nuxt'],
  kv: {
    driver: 'cloudflare-kv-binding',
    binding: 'KV',
    namespaceId: '<kv-namespace-id>',
  },
})

Set the Namespace ID

Pass namespaceId in config:

kv: {
  driver: 'cloudflare-kv-binding',
  namespaceId: '<kv-namespace-id>',
}

Or set KV_NAMESPACE_ID in the build environment:

KV_NAMESPACE_ID=<kv-namespace-id>

When namespaceId is present, the Nitro module adds the namespace to Cloudflare Wrangler config:

cloudflare: {
  wrangler: {
    kv_namespaces: [
      { binding: 'KV', id: '<kv-namespace-id>' },
    ],
  },
}

Use a Custom Binding Name

The default binding is KV. Set binding when the Cloudflare resource uses another name:

kv: {
  driver: 'cloudflare-kv-binding',
  binding: 'APP_KV',
  namespaceId: '<kv-namespace-id>',
}

The runtime driver reads from that Cloudflare binding.

Let Hosting Select Cloudflare

When hosting resolves to Cloudflare and no explicit driver is set, ViteHub selects cloudflare-kv-binding automatically:

export default defineNitroConfig({
  modules: ['@vitehub/kv/nitro'],
})

Explicit kv.driver still wins. Use explicit config when you want local fs-lite behavior or need a custom binding.

Verify the Provider

Write a value:

curl -X PUT https://<your-worker>/api/settings

Read it back:

curl https://<your-worker>/api/settings

Expected response:

{
  "settings": {
    "enabled": true
  }
}