-
-
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
[v8] Merge @sentry-internal/tracing
into @sentry/core
#9885
Milestone
Comments
Closed
This was referenced Mar 5, 2024
Merged
AbhiPrasad
added a commit
that referenced
this issue
Mar 5, 2024
This was referenced Mar 18, 2024
AbhiPrasad
added a commit
that referenced
this issue
Mar 22, 2024
This functionality is no longer being used, so we can remove it and it's tests. Part of #9885 since it makes it easier to port over browsertracing into browser package.
c298lee
pushed a commit
that referenced
this issue
Mar 22, 2024
This functionality is no longer being used, so we can remove it and it's tests. Part of #9885 since it makes it easier to port over browsertracing into browser package.
c298lee
pushed a commit
that referenced
this issue
Mar 23, 2024
This functionality is no longer being used, so we can remove it and it's tests. Part of #9885 since it makes it easier to port over browsertracing into browser package.
AbhiPrasad
added a commit
that referenced
this issue
Apr 5, 2024
This PR creates a `browser-utils` package that contains browser specific utils that can be shared between the browser, replay, and feedback packages. Eventually we will move `browserTracingIntegration` outside of this package, but the instrumentation handlers will remain here. We will also move the browser related utils in `@sentry/utils` to this package. Given this removes `@sentry-internal/tracing` entirely, it is a part of #9885 ref #9832
cadesalaberry
pushed a commit
to cadesalaberry/sentry-javascript
that referenced
this issue
Apr 19, 2024
This functionality is no longer being used, so we can remove it and it's tests. Part of getsentry#9885 since it makes it easier to port over browsertracing into browser package.
cadesalaberry
pushed a commit
to cadesalaberry/sentry-javascript
that referenced
this issue
Apr 19, 2024
This PR creates a `browser-utils` package that contains browser specific utils that can be shared between the browser, replay, and feedback packages. Eventually we will move `browserTracingIntegration` outside of this package, but the instrumentation handlers will remain here. We will also move the browser related utils in `@sentry/utils` to this package. Given this removes `@sentry-internal/tracing` entirely, it is a part of getsentry#9885 ref getsentry#9832
cadesalaberry
pushed a commit
to cadesalaberry/sentry-javascript
that referenced
this issue
Apr 19, 2024
This PR moves `browserTracingIntegration` into the browser package, leaving `browser-utils` only existing purely for utils/instrumentation (and our vendored web vitals implementation). resolves getsentry#9885
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In v8, let's merge tracing-internals into core, and stop publishing
@sentry-internal/tracing
.Tasks
@sentry/tracing
package #8796instrumentRoutingWithDefaults
#11240The text was updated successfully, but these errors were encountered: