ViteHub is still experimental. Expect bugs and breaking changes.

Provider output

Reference generated deployment and runtime artifacts owned by ViteHub package integrations.

Provider Output is generated deployment or runtime artifacts required by a provider. It belongs to the package that owns the primitive and should not become application authoring surface.

Output families

OutputProviderOwnerPurpose
Worker bundleCloudflarePackage integration using Cloudflare outputRuns server or primitive runtime code in Workers.
wrangler.json entriesCloudflareBlob, Database, Queue, Schedule, Workflow, Sandbox, Agent state as applicableDeclares bindings, crons, durable objects, queues, and other worker config.
Vercel Build OutputVercelPackage integration using Vercel outputWrites functions, static files, routes, and function config under .vercel/output.
Generated Runtime RegistryLocal and hostedPackage that discovers DefinitionsMaps Discovery Identity to lazy-loaded Definitions.
Generated Nitro handler or pluginNitro-shaped hostsPackage that requires a host bridgeRegisters package-owned routes or runtime hooks.
Provision StateLocal development and build inputViteHub CLI plus package Provision StepsStores non-secret provider ids under .vitehub/provision.json.

Generation timing

Provider Output is written during production-shaped builds. Vite dev usually proves discovery and local generated files; builds prove deployable host artifacts.

Terminal
pnpm build
find .vitehub -maxdepth 4 -type f | sort
find .vercel/output -maxdepth 4 -type f | sort
find dist -maxdepth 4 -type f | sort

Provider Output Contracts

Provider Output Contracts assert generated artifact shape without deploying to a cloud account. Use them for bindings, emitted functions, generated worker config, bundle purity, cron entries, and selected provider dependency reachability.

Terminal
pnpm --filter @vite-hub/database test
pnpm --filter @vite-hub/workflow test

Public boundary

Application code should import Runtime Helpers and stable handlers. Generated Provider Output may import generated files, virtual modules, or provider runtime packages internally.

DoAvoid
Call runQueue('welcome-email', payload).Import a generated queue consumer from .vitehub.
Import useServerEnv() from #vitehub/env/server.Import .vitehub/env/server.mjs directly.
Inspect .vercel/output during deployment debugging.Treat .vercel/output files as source files to edit.
Copyright © 2026