-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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(v8/replay): Deprecate @sentry/replay
exports
#11243
Conversation
size-limit report 📦
|
@sentry/replay
exports
/** @deprecated Use the export from `@sentry/replay` or from framework-specific SDKs like `@sentry/react` or `@sentry/vue` */ | ||
export type { ReplayEventType } from './types'; |
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.
Do JSDoc comments work like this? I think we need to add the comments to the actual declarations of the exported items.
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.
That's true! I fixed it in #11242 by exporting an internal variable that can be re-exported from @sentry/browser
and also exporting the deprecated value.
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.
This made me think. We don't have to deprecate anything in v8. We can just remove it.
ref #11200
on v7 #11242