Client always bundles log/metric flush code #26145

The Client constructor in packages/core/src/client.ts (L318–327) always calls setupWeightBasedFlushing for both logs and metrics. That statically pulls _INTERNAL_flushLogsBuffer / _INTERNAL_flushMetricsBuffer, the log and metric envelope builders, and the size estimators into every bundle, even when an app never captures a log or metric.

• Measured with esbuild 0.27.7 (minify, ESM, platform browser, __SENTRY_DEBUG__: false) on a tracing-only setup (BrowserClient + browserTracingIntegration, setCurrentClient, client.init()): 2,068 B raw / 445 B br-11 of this code (131,185 B raw total).
• Related but different: Client.flush() leaks log/metric flush timers when client has no transport #20206 and Metrics flush timer should use .unref() to not block process exit #19171 are about the flush timers' runtime behavior.

via @BYK.

--

View Session in Sentry