-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
ref(replay): Move @sentry/replay
code to @sentry-internal/replay
#11200
Conversation
0a56cb3
to
ccee1e2
Compare
size-limit report 📦
|
- [Change of Replay default options (`unblock` and `unmask`)](./MIGRATION.md#change-of-replay-default-options-unblock-and-unmask) | ||
- [Angular Tracing Decorator renaming](./MIGRATION.md#angular-tracing-decorator-renaming) |
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.
I saw that there is a TOC for every sub-heading so I added the missing ones :)
76262a0
to
d86ab94
Compare
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.
So I think we need to split up and target parts of this PR to the v7
branch. Deprecating exports from @sentry/replay
on develop
won't really do anything because we're going to remove this package anyway in v8.
So I suggest we
- introduce the deprecations in v7. I think just the deprecation in v7 should be enough because the replacement for users is to directly import the APIs and types from
@sentry/browser
(or SDKs building on top of browser). The internal package should just be for us. - Rename the
@sentry/replay
package to@sentry-internal/replay
package indevelop
(v8).
As an alternative, if you prefer, we can also already introduce this package in v7 but we'd need to worry about releasing it in v7 correctly then, too.
WDYT, does this make sense?
# TODO: Check if we can re-introduce linting in demo | ||
demo |
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.
ahh right there's a demo 😅 I think it's fine to leave it as-is
packages/replay/src/index.ts
Outdated
/** @deprecated Import from `@sentry-internal/replay` */ | ||
export const getReplay = internalGetReplay; |
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.
m: Since this is (potentially) user-facing, the replacement should be to import from @sentry/browser
or framework SDK instead of from @sentry-internal/replay
.
For us internally, it's fine to eslint-ignore the deprecations in v7
as long as we don't have the @sentry-internal/replay
package.
d86ab94
to
5772fbd
Compare
'@sentry/replay': | ||
access: $all | ||
publish: $all | ||
unpublish: $all | ||
# proxy: npmjs # Don't proxy for E2E tests! |
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.
I was able to just delete this (instead of renaming), as there is '@sentry-internal/*'
further down.
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.
LGTM!
I'm having issues testing this new replay package locally (e.g. in sentry). When I yarn, it complains because the package isn't published to npm:
|
closes #9165