BrowserTracing id property missing in v7

[AbhiPrasad]

Discussed in #5635

^{Originally posted by martinkwan August 26, 2022}
Hi, I am trying to check if Sentry's APM is initialized with this line of code.

import * as Sentry from '@sentry/react';
import {Integrations as TracingIntegrations} from '@sentry/tracing';

Sentry.getCurrentHub()
      .getClient()
      ?.getIntegration(TracingIntegrations.BrowserTracing)

This worked in v6, but while migrating to v7 BrowserTracing removed it's ID property and now Typescript is giving me this error:

Argument of type 'typeof BrowserTracing' is not assignable to parameter of type 'IntegrationClass<BrowserTracing>'.
  Property 'id' is missing in type 'typeof BrowserTracing' but required in type 'IntegrationClass<BrowserTracing>'.

Is there fix for this typescript error? I know the static property id is removed in v7 from BrowserTracing

[AbhiPrasad]

So - we intentionally don't use the id here for treeshaking purposes:

sentry-javascript/packages/tracing/src/browser/browsertracing.ts

Lines 124 to 127 in f563eae

	// This class currently doesn't have a static `id` field like the other integration classes, because it prevented
	// @sentry/tracing from being treeshaken. Tree shakers do not like static fields, because they behave like side effects.
	// TODO: Come up with a better plan, than using static fields on integration classes, and use that plan on all
	// integrations.

We should find a workaround though to unblock the user.

[lforst]

Of course, this is very dirty but just to unblock: We have getIntegrationById() on the BaseClient, meaning if we applied a sprinkle of @ts-ignore we could do Sentry.getCurrentHub().getClient()?.getIntegrationById('BrowserTracing').

I knew this change would bite us in the butt some day - sorry about that.