Config options

Integration Options configure ViteHub package integrations. Provider Selection belongs in Integration Options when it changes generated output, bindings, imports, or deployment behavior.

Built-in deployment preset

vitehub() requires exactly one built-in preset: cloudflare, netlify, vercel, deno, or node. The selection is the single source for host identity, runtime, Nitro output, packaging, and built-in Blob, Queue, Rate Limit, and Sandbox adapters. Conflicting Nitro or hosting environment selections fail configuration.

name is ViteHub's logical deployment identity. Cloudflare Workers Builds supplies its connected Worker through WRANGLER_CI_OVERRIDE_NAME, which the Cloudflare preset resolves below explicit name and above the nearest package.json name and Vite root directory name. A differing explicit ViteHub identity fails because the connected Worker remains the deployment target. Cloudflare uses the resolved identity for default Worker, Blob bucket, Queue prefix, Rate Limit namespace, Sandbox, and Container names. Explicit Wrangler Worker names remain authoritative outside Workers Builds, while explicit Blob bucket, driver, or store options still win. This fallback derives deterministic names but does not provision the corresponding R2 bucket or Queue. The generated deployment manifest records the resolved identity and its source.

Unsupported requested capabilities fail before a production build can silently select a weaker provider. The node preset intentionally exposes its filesystem Blob store as single-host and its memory Rate Limiter as single-process. The deno preset rejects Schedule and agent.runtime: "deno" because those generated servers are not part of its deployed Nitro entrypoint. Deno output includes runtime package staging, a validated deployment manifest, and a non-interactive create-or-update runner.

Direct hubX() integration functions remain available from their independent @vite-hub/*/vite owner-package paths.

The root vitehub() facade enables Agent, Blob, Browser, Channels, Database, KV, Queue, Rate Limit, Sandbox, Schedule, Workflow, and Workspace with true. Email accepts true with the Cloudflare preset, where it selects the Cloudflare Email driver; other presets reject that boolean default and require explicit provider options. Direct owner-package integrations retain their detailed option types. Auth follows the same opt-in shape but currently has no plugin option bag.

Vite Integration options

Option placement

Provider-specific driver fields are intentionally summarized here. Read the exported package types when configuring a deep provider adapter, and keep provider choices in Integration Options unless the owning package documents an invocation-time option.

Agent eval options

Agent Eval Runner defaults live under the Agent Package integration.

import { defineConfig } from 'vite'
import { vitehub } from 'vite-hub'

export default defineConfig({
  plugins: [
    vitehub({
      preset: "node",
      agent: {
        eval: {
          cache: true,
          maxConcurrency: 2,
          scoreThreshold: 85,
          testTimeout: 60_000,
        },
      },
    }),
  ],
})

Env options

Env separates Public Env, compile-time define values, and Server Env. Secret Env values belong in env.server, not env.public or env.define.

import { defineConfig } from 'vite'
import { vitehub } from 'vite-hub'
import { env } from 'vite-hub/env'

export default defineConfig({
  plugins: [vitehub({ preset: "node", env: { diagnostics: 'summary' } })],
  env: {
    public: {
      appName: env({ default: 'Acme' }),
    },
    server: {
      apiToken: env({ secret: true, source: env.source('API_TOKEN') }),
    },
  },
})

Related

• Vite
• Runtime and host support
• Provisioning
• Provider output