feat(js): Import BrowserTracing directly from a browser SDK

[AbhiPrasad]

ref getsentry/sentry-javascript#5815

Docs for changes in getsentry/sentry-javascript#7342 that was just released with 7.44.0.

This PR updates our instructions to remove the dependency on using the @sentry/tracing package for the frontend JS SDKs. Instead users can now just import BrowserTracing directly from a package.

Basically from:

import * as Sentry from '@sentry/browser';
import { BrowserTracing } from '@sentry/tracing';

Sentry.init({
  dsn: '__DSN__',
  tracesSampleRate: 1.0,
  integrations: [new BrowserTracing()],
});

to

import * as Sentry from '@sentry/browser';

Sentry.init({
  dsn: '__DSN__',
  tracesSampleRate: 1.0,
  integrations: [new Sentry.BrowserTracing()],
});

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
sentry-docs	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Mar 30, 2023 at 9:54AM (UTC)

[lizokm]

Made a few suggestions.

[AbhiPrasad]

Plan is now to merge this in next week!

[timfish]

I found these changes too but didn't put them in my PR because they're browser related.

3 of the 4 file changes are simply replacing .getCurrentHub().getScope().getTransaction() with .getActiveTransaction() and could arguably go in another PR.

However there was also a yarn add tracing left in /src/platform-includes/performance/enable-tracing/javascript.mdx which can be seen here.

[AbhiPrasad]

Sorry for the ping folks - had a busted git merge that I needed to repair.