[Replay] Migrating sentry-replay into JS SDK mono-repo

Problem Statement

There is the sentry-replay repo which has the Sentry Browser SDK package and rreweb packages as dependencies.

Meaning it has clear requirement dependancies, and similar requirement for CI/CD in terms of testing and creating releases, but cannot easily take advantage of everything which is already part of the JS SDK.

Possible benefits of moving into the JS mono-repo

• existing test infrastructure
• monitor file size over across changes
• existing releases
• could simplify reuse of code from within the JS SDK and for users to instrument in the future

Concerns: Adds more dependencies into the JS repo, where there is already quite a number of integrations for different browser and Node frameworks, along with all the Sentry features, and SDKs which are dependant on the JS SDK (Electron and react-native)

Solution Brainstorm

Include sentry-replay to be more tightly coupled as part of the Sentry JavaScript SDK mono-repo

Outcomes:

• https://github.com/getsentry/sentry-replay included in sentry-javascript monorepo
  • can we define here what the ideal import and init will look like? @jas-kas
• @sentry/replay is available via the CDN bundle (e.g. combined bundle w/ @sentry/browser)
• Available via lazy loader

Progress

Phase I: Pre-Migration

• https://github.com/getsentry/sentry-replay/issues/311

Phase II: Migration

• https://github.com/getsentry/sentry-javascript/issues/6257
• #6280
• Release first official 7.x version from monorepo
• https://github.com/getsentry/sentry-javascript/issues/6383
• https://github.com/getsentry/sentry-javascript/pull/6335

Phase III: Post-Migration

• https://github.com/getsentry/sentry-javascript/issues/6285
• #6362

More long-term tasks are tracked in

• #6458
• https://github.com/getsentry/sentry-javascript/issues/6459

[smeubank]

@billyvg and @jas-kas we can already start collaborating here if we need to add to this issue, or split it up

[vladanpaunovic]

One important decision to be made here. Does @sentry/replay follow the same versioning structure as the rest of the repo? If it doesn’t we need to adjust our publishing process around that!

I discussed this with @benvinegar and we agreed that @sentry/replay will follow the same versioning structure as the rest of the monorepo.

We will make sure to highlight in docs and release notes that this is still in alpha before jumping into a stable version.