import tracer from 'dd-trace';
/**
 * WARNING to projects importing this
 * Even if dd-tracer documents that instrumentation happens at **.init() time**
 * (see https://docs.datadoghq.com/tracing/trace_collection/automatic_instrumentation/dd_libraries/nodejs/#import-and-initialize-the-tracer ),
 *   1. dd-tracer has no choice but to do some stuff **at import time**
 *   2. dd-tracer is not exempt from bugs, like https://github.com/DataDog/dd-trace-js/issues/5211
 *
 * So, do not assume that dd-trace is *fully off* by default! Some of it runs!
 * If you want to entirely disable all of dd-trace (e.g. during unit tests),
 * then you must set `DD_TRACE_ENABLED=false`
 *
 * Q: Why not move the dd-trace import inside the `if DD_TRACE_ENABLED` condition, then?
 * A: Because the future is ESM, and ESM imports must be static and top-level.
 */
export declare const DD_TRACER: tracer.Tracer;