Skip to main content
This page configures browser capture in Next.js, Vite + React, and TanStack Start. For server processes, use the Node.js options or NestJS options.

Service names

Give each process a stable service name, such as storefront or checkout-worker:
The surface public key selects the app receiving telemetry. The service name identifies the process within that telemetry.

Environments

Set INTERFERE_ENVIRONMENT to your deployment label:
Next.js and Vite stamp the value into the build. It does not need a NEXT_PUBLIC_ or VITE_ prefix. Without an explicit value, the SDK falls back to VERCEL_ENV, then NODE_ENV, then development. Interfere filters local-like environments such as development, local, and test before ingestion. Use a deployment label such as staging for verification, or change environment filtering for the surface.

Capture features

Configure features on the InterfereProvider you added during installation. Import it from @interfere/next/provider for Next.js or @interfere/vite/provider for Vite and TanStack Start. All features default to enabled, subject to consent. For example, disable replay and page events:
Set init({ tracing: false }) to omit browser tracing. Set errorBoundary={false} on the provider if you already report React render errors through another boundary.

Custom ingest domain

Configure a subdomain for telemetry if requests to the default endpoint are blocked by browser extensions. Add the CNAME using the target shown in your dashboard, then set apiHost. For Next.js:
next.config.ts
For Vite, pass apiHost to the build plugin:
Interfere provisions TLS for the domain. Telemetry requests do not send cookies.