Documentation

The build fetches your public policy once and bundles it, so the server never fetches it at runtime.

consentManifest() from c15t/vue/vite downloads the policy during vite build, when the app uses manifest(), and in vite dev when the app first loads it:

import vue from '@vitejs/plugin-vue';
import { consentManifest } from 'c15t/vue/vite';
import { defineConfig } from 'vite';

export default defineConfig({ plugins: [vue(), consentManifest()] });

Without a backendURL option, the plugin reads VITE_C15T_BACKEND_URL, then VITE_INTH_PROJECT_URL, from the environment or .env. manifest() from c15t/vue/vue-plugin, with no options, reads the downloaded policy and the same backend URL, so src/main.ts needs no import from c15t/generated:

import { c15tVue, manifest } from 'c15t/vue/vue-plugin';

app.use(c15tVue, { mode: manifest(), scripts });

The browser resolves the visitor's policy from the bundled snapshot, with no /manifest request. When the policy depends on the visitor's country or region and neither inputs nor geoURL supplies one, the browser asks the backend's /init instead. The app bundles the policy and English copy, and loads the resolver as its own chunk when it needs it.

When the build has no snapshot, as in vite dev after a failed download, manifest() fetches ${backendURL}/manifest when the app starts.

The snapshot is fixed at build time:

• Rebuild after changing policies, translations or vendors. If your CI caches build output, force a fresh build.
• Consent choices still go to the backend.

The build reads the backend URL from your public backend URL variable when the config doesn't pass one: NEXT_PUBLIC_C15T_BACKEND_URL in Next.js, NUXT_PUBLIC_C15T_BACKEND_URL in Nuxt, PUBLIC_C15T_BACKEND_URL in Astro, Svelte and SvelteKit, and VITE_C15T_BACKEND_URL in TanStack Start and other Vite apps. Each also reads the matching Inth variable, such as NEXT_PUBLIC_INTH_PROJECT_URL, when the c15t one is unset. See set the backend URL.

The fetch waits at most 10 seconds. When it fails, or no backend URL is set, every framework does the same thing:

Set onBuildError to use one behaviour for both. 'fail' stops dev too. 'runtime' lets a production build finish, and the server fetches the policy at runtime. The C15T_ON_BUILD_ERROR environment variable overrides the option, so you can deploy during a backend outage without a code change:

C15T_ON_BUILD_ERROR=runtime npm run build

Turborepo's strict environment mode hides undeclared variables from tasks, so list C15T_ON_BUILD_ERROR in the build task's passThroughEnv there.

The build skips the fetch, without an error, when it can't use a snapshot, for example when the backend URL is relative. With onBuildError: 'fail', a relative URL stops the build. Consent modes lists every case.

vite build and vite dev fetch the manifest when they start. vite preview serves the last build without fetching. The plugin writes no file into your app, so there is nothing to keep out of Git. c15t/generated ships its own types, so tsc, vue-tsc and svelte-check pass on a fresh checkout without a build first.

The plugin can't see the options your app passes to manifest(). When the app passes source: 'runtime' or manifestURL, set consentManifest({ source: 'runtime' }) too. The build then downloads no manifest, so it doesn't fail when the backend's /manifest is down.

For policy edits without a rebuild, use hosted() or manifest({ source: 'runtime' }).