FlowTracer Configuration

FlowTracer configuration spans build-time instrumentation, runtime startup, and runtime control. Use this page to choose the right FlowTracer path, then use the linked reference pages for exact setting behavior.

Keep Flow tracing out of publicly accessible builds. The normal use case is local development and restricted internal test or QA environments.

Recommended Integration Paths

Vite

Use @autotracer/plugin-vite-flow for Vite apps.

This is the normal path for browser apps because the plugin handles build-time instrumentation and can inject the runtime imports used by @autotracer/flow and @autotracer/flow/runtime.

Use these pages together:

• Vite installation
• FlowTracer Vite settings
• @autotracer/plugin-vite-flow
• FlowTracer runtime settings

Next.js And Other Babel Builds

Use @autotracer/plugin-babel-flow for build-time instrumentation, then lazy-load @autotracer/flow in your bootstrap entry when you want immediate startup or lazy-load @autotracer/flow/runtime when you want dormant startup.

Use these pages together:

• Next.js installation
• FlowTracer Babel settings
• @autotracer/plugin-babel-flow
• @autotracer/flow
• FlowTracer runtime settings

Manual Tracer Path

For normal browser integrations, do not start with createFlowTracer(logger, config?).

Use that factory only for manual harnesses and other custom tracer setups where you are creating the tracer instance yourself.

For that path, use:

• @autotracer/flow
• theme

Reference Pages

• FlowTracer runtime settings for runtime startup, dormant mode, browser control, and the normal app path
• theme for the manual tracer createFlowTracer(logger, config?) theme option
• FlowTracer Vite settings for Vite build-time settings and Vite pragma comments
• FlowTracer Babel settings for Babel build-time settings and Babel pragma comments
• FlowTracer Theme API for Vite theme files used by the global tracer
• FlowTracer Example Themes for copyable theme file examples
• @autotracer/flow for the runtime package API, including globalThis.autoTracer.flowTracer
• @autotracer/plugin-vite-flow for the Vite package surface
• @autotracer/plugin-babel-flow for the Babel package surface

Browser Control

For browser-based internal web apps, use the Dashboard workflow when it is mounted.

When the Dashboard is not available, use the lower-level runtime API on globalThis.autoTracer.flowTracer.