-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(session replay): introduce standalone version of session replay #559
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Mostly focused on the interface changes. Left comments/questions/thoughts mostly to help me understand some implications. Nothing blocking for the initial test version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kwalker3690 I think it would be good to see how this standalone version integrates with the plugin before releasing the standalone package, but ok releasing it if it makes the PRs cleaner.
@justin-fiedler yes! please see #555, also linked in the description. I think I have to merge this one first separately to be able to reference the built @amplitude/session-replay-browser from the plugin, the build currently fails because that package doesn't exist yet |
Summary
This PR introduces a standalone version of the session replay SDK, that will also used by the existing plugin. There should be no functional changes in separating this to it's own package. This will allow us to support customers who want to use session replay who aren't instrumented through the browser SDK.
Please take a look at this closed PR which includes how the standalone SDK will be used in the plugin: #555. I will make a revision to incorporate the changes into the plugin once this PR has merged.
Checklist