remove so much fluff comments. i hate clankers

Author: Lms24

packages/astro/src/index.types.ts

@@ -21,9 +21,6 @@ export declare function init(options: Options | clientSdk.BrowserOptions | NodeO
 export declare const linkedErrorsIntegration: typeof clientSdk.linkedErrorsIntegration;
 export declare const contextLinesIntegration: typeof clientSdk.contextLinesIntegration;
 export declare const spanStreamingIntegration: typeof clientSdk.spanStreamingIntegration;
-// The client entry serves the `@sentry/core/browser` span-start APIs, which install span streaming
-// on first use; the server entry serves the plain `@sentry/core` ones. Same signatures, but the
-// star exports above are ambiguous without these.
 export declare const startSpan: typeof clientSdk.startSpan;
 export declare const startSpanManual: typeof clientSdk.startSpanManual;
 export declare const startInactiveSpan: typeof clientSdk.startInactiveSpan;

packages/core/src/browser-exports.ts

@@ -3,21 +3,15 @@
  *
  * @module
  */
-// These share their names with the plain variants in `server-exports`, but additionally make sure
-// the browser span streaming integration is installed on the client before the span starts. That
-// indirection is what lets error-only browser bundles tree-shake span streaming away entirely:
-// `init()` never references the integration, so it's only retained when span-creating code is.
-//
-// `@sentry/core` pins these names to the plain variants (see `index.ts`); `@sentry/core/browser`
-// serves the guarded ones. Browser-facing packages therefore upgrade by importing from
-// `@sentry/core/browser` — no call site changes.
+
 export {
   startSpan,
   startInactiveSpan,
   startSpanManual,
   startIdleSpan,
   _INTERNAL_ensureBrowserSpanStreaming,
 } from './tracing/browserSpanApi';
+
 export { spanStreamingIntegration } from './integrations/browserSpanStreaming';
 
 export {

packages/core/src/index.ts

@@ -2,10 +2,9 @@ export * from './shared-exports';
 export * from './server-exports';
 export * from './browser-exports';
 
-// `server-exports` and `browser-exports` both export these names (plain vs. browser-guarded
-// variants). Explicit re-exports shadow the otherwise-ambiguous star exports and pin the root entry
-// to the plain/server variants. Without them, importing any of these from `@sentry/core` is a
-// link-time `SyntaxError: ... contains conflicting star exports`.
+// `server-exports` and `browser-exports` both export these APIs.
+// We need to re-export them here to disambiguate the exports for anyone importing
+// from `@sentry/core`. Server exports win over browser exports.
 export { startSpan, startInactiveSpan, startSpanManual } from './tracing/trace';
 export { startIdleSpan } from './tracing/idleSpan';
 export { spanStreamingIntegration } from './integrations/spanStreaming';

packages/core/src/server-exports.ts

@@ -4,11 +4,7 @@
  * @module
  */
 
-// The span-start APIs and the span streaming integration exist in two variants under the same name:
-// the plain ones here, and span-streaming-aware ones in `browser-exports`. See `browser-exports.ts`.
 export { startSpan, startInactiveSpan, startSpanManual } from './tracing/trace';
-// `startIdleSpan` has no server consumer, but `@sentry/core` re-exports it — routing it through here
-// keeps the root entry's surface unchanged.
 export { startIdleSpan } from './tracing/idleSpan';
 export { spanStreamingIntegration } from './integrations/spanStreaming';
 

packages/core/src/tracing/browserSpanApi.ts

@@ -18,13 +18,9 @@ import {
  * actually start a span. `@sentry/browser`'s `init()` deliberately doesn't reference spanStreamingIntegration,
  * so error-only apps tree-shake the entire span streaming graph away without needing
  * the `__SENTRY_TRACING__` flag.
- *
- * The names deliberately match the core originals: `@sentry/core/browser` serves these guarded
- * variants, `@sentry/core` serves the plain ones, so browser-facing packages upgrade by changing
- * only the import specifier.
  */
 
-const installed = new WeakSet<Client>();
+const clientsWithIntegration = new WeakSet<Client>();
 
 /**
  * Lazily install the browser span streaming integration.
@@ -37,11 +33,11 @@ const installed = new WeakSet<Client>();
 export function _INTERNAL_ensureBrowserSpanStreaming(client: Client | undefined = getClient()): void {
   // The `WeakSet` is an allocation optimization, not a semantic gate — `addIntegration()` is already
   // idempotent by integration name, including against a user-supplied instance.
-  if (!client || installed.has(client) || !hasSpanStreamingEnabled(client)) {
+  if (!client || clientsWithIntegration.has(client) || !hasSpanStreamingEnabled(client)) {
     return;
   }
 
-  installed.add(client);
+  clientsWithIntegration.add(client);
   client.addIntegration(spanStreamingIntegration());
 }
 

packages/core/src/tracing/index.ts

@@ -17,9 +17,6 @@ export {
   SPAN_STATUS_OK,
   SPAN_STATUS_UNSET,
 } from './spanstatus';
-// Note: `startSpan`, `startInactiveSpan`, `startSpanManual` and `startIdleSpan` are deliberately
-// not re-exported here. They exist in a plain variant (`server-exports`) and a span-streaming-aware
-// variant (`browser-exports`) under the same name — see `browser-exports.ts` for why.
 export {
   _INTERNAL_startInactiveSpan,
   continueTrace,

packages/effect/src/index.types.ts

@@ -22,9 +22,6 @@ export declare function init(options: Options | clientSdk.BrowserOptions | serve
 export declare const linkedErrorsIntegration: typeof clientSdk.linkedErrorsIntegration;
 export declare const contextLinesIntegration: typeof clientSdk.contextLinesIntegration;
 export declare const spanStreamingIntegration: typeof clientSdk.spanStreamingIntegration;
-// The client entry serves the `@sentry/core/browser` span-start APIs, which install span streaming
-// on first use; the server entry serves the plain `@sentry/core` ones. Same signatures, but the
-// star exports above are ambiguous without these.
 export declare const startSpan: typeof clientSdk.startSpan;
 export declare const startSpanManual: typeof clientSdk.startSpanManual;
 export declare const startInactiveSpan: typeof clientSdk.startInactiveSpan;

packages/nuxt/src/index.types.ts

@@ -17,9 +17,6 @@ export declare function init(options: Options | SentryNuxtClientOptions | Sentry
 export declare const linkedErrorsIntegration: typeof clientSdk.linkedErrorsIntegration;
 export declare const contextLinesIntegration: typeof clientSdk.contextLinesIntegration;
 export declare const spanStreamingIntegration: typeof clientSdk.spanStreamingIntegration;
-// The client entry serves the `@sentry/core/browser` span-start APIs, which install span streaming
-// on first use; the server entry serves the plain `@sentry/core` ones. Same signatures, but the
-// star exports above are ambiguous without these.
 export declare const startSpan: typeof clientSdk.startSpan;
 export declare const startSpanManual: typeof clientSdk.startSpanManual;
 export declare const startInactiveSpan: typeof clientSdk.startInactiveSpan;

packages/react-router/src/index.types.ts

@@ -17,9 +17,6 @@ export declare function init(options: Options | clientSdk.BrowserOptions | serve
 export declare const contextLinesIntegration: typeof clientSdk.contextLinesIntegration;
 export declare const linkedErrorsIntegration: typeof clientSdk.linkedErrorsIntegration;
 export declare const spanStreamingIntegration: typeof clientSdk.spanStreamingIntegration;
-// The client entry serves the `@sentry/core/browser` span-start APIs, which install span streaming
-// on first use; the server entry serves the plain `@sentry/core` ones. Same signatures, but the
-// star exports above are ambiguous without these.
 export declare const startSpan: typeof clientSdk.startSpan;
 export declare const startSpanManual: typeof clientSdk.startSpanManual;
 export declare const startInactiveSpan: typeof clientSdk.startInactiveSpan;

packages/remix/src/index.types.ts

@@ -19,9 +19,6 @@ export declare const browserTracingIntegration: typeof clientSdk.browserTracingI
 export declare const linkedErrorsIntegration: typeof clientSdk.linkedErrorsIntegration;
 export declare const contextLinesIntegration: typeof clientSdk.contextLinesIntegration;
 export declare const spanStreamingIntegration: typeof clientSdk.spanStreamingIntegration;
-// The client entry serves the `@sentry/core/browser` span-start APIs, which install span streaming
-// on first use; the server entry serves the plain `@sentry/core` ones. Same signatures, but the
-// star exports above are ambiguous without these.
 export declare const startSpan: typeof clientSdk.startSpan;
 export declare const startSpanManual: typeof clientSdk.startSpanManual;
 export declare const startInactiveSpan: typeof clientSdk.startInactiveSpan;