ReactTracer Runtime Settings
Package: @autotracer/react18 · Layer: Runtime · Type: Overview
Start here before changing individual settings in isolation.
Tree Visibility
Trigger Sessions
Startup And Appearance
include* = includeMount, includeRendered, includeReconciled, and includeSkipped.
Prop Noise
Use skippedObjectProps when prop output is dominated by framework objects, styling props, or callback props that are not useful for the debugging question in front of you.
This setting only reduces ReactTracer prop-output noise for exact component-name matches. It is not meant for suppressing user identifiers in production environments.
Non-Overrides
detectIdenticalValueChanges adds warnings only to nodes that are already visible. It does not override the include* visibility settings or filterEmptyNodes.
Start Here
If components are missing, read maxFiberDepth, includeNonTrackedBranches, the four include* visibility settings above, and then filterEmptyNodes.
If collapsed markers are confusing, read filterEmptyNodes together with showLevelDetails.
If prop output is noisy, read skippedObjectProps before treating repeated prop churn as a meaningful signal.
If trigger-driven sessions behave unexpectedly, read enabled, startTriggerFunctionName, endTriggerFunctionName, endTriggerMode, and triggerRearmMode together.
If tracing starts correctly but the output format or styling is wrong for your workflow, read enabled, outputMode, and colors together. If you use the Vite plugin, also see ReactTracer Theme API and ReactTracer Example Themes, where local theme files can override overlapping project defaults.
The remaining lower-priority settings mainly affect diagnostics or specialized workflows: showFlags, internalLogLevel, and trackedStateResolution.