-
-
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 Release Plan #9508
Comments
Will the team try to reduce the bundle size in v8? |
@m1heng by removing deprecated parts of the SDK, we'll be able to reduce some size. Maybe also by the proposed hub/scope changes. However, at this time, we haven't planned a big bundle size reduction intiative as in v7. |
Task list to remove internal usage of deprecated APIs: #10100 |
Could you please pay more attention to updating documentation: getsentry/sentry-docs#8953 |
Docs issues tracked with: #11064 |
ref #9508 The `BrowserApiErrors` integration interfers with Angular error handler, so don't include it in the default integrations.
I removed Remove Tried it in v7, no dice. I guess v8 isn't it yet either 😢. One day!! |
First beta version is out! https://github.com/getsentry/sentry-javascript/releases/tag/8.0.0-beta.1 |
@AbhiPrasad Hi! Excited about v8 beta! Could you please take a look at pr for updating @sentry/nextjs to v8-beta in my project. Faced few issues while updating. I left questions about them in pr. |
ref getsentry#9508 The `BrowserApiErrors` integration interfers with Angular error handler, so don't include it in the default integrations.
Is there an ETA for v8 integration in Sentry.io (whether it is beta or not)? I'm thinking of using Sentry, but I'm still deciding whether I should wait for v8, or adopt for v7 now |
v8 is almost ready, unless any issues pop up in the beta (which we don't forsee right now) we expect to do a stable release next week! |
Since we shipped this, I am closing this - we can keep track of other stuff elsewhere! 🎉 |
This issue collects concrete things we know we want to include/do in v8 for sure. We have a lot of things captured already in various places, but not all of these things will necessarily happen in v8. The goal of this issue is to have a proper overview.
For feedback please reach out via GH discussions.
Main user facing changes
The biggest changes, from an SDK user perspective, are the changes to performance APIs:
All Changes
Version support
@sentry/vite-plugin
in@sentry/sveltekit
& stop exposing options directly #9835@sentry/webpack-plugin
in@sentry/nextjs
& stop exposing options directly #9836@sentry/webpack-plugin
in@sentry/gatsby
& stop exposing options directly #9837Update meta SDKs to use OpenTelemetry
@sentry/nextjs
to be powered by OpenTelemetry #11042@sentry/astro
to be powered by OpenTelemetry #11039@sentry/remix
to be powered by OpenTelemetry #11040@sentry/sveltekit
to be powered by OpenTelemetry #11041Package changes
@sentry/hub
package #5665@sentry/tracing
package #8796@sentry/integrations
into@sentry/core
#9833@sentry-internal/tracing
into@sentry/core
#9885@sentry/utils
into@sentry/core
#9832@sentry/replay
#9834@sentry/opentelemetry-node
package #9843@sentry-internal/feedback
#9886Integrations
Sentry.Integrations
hash in favor of top-level exports #8844TryCatch
integration #8838RewriteFrames
not functional in browser environments #6423BrowserTracing
routing instrumentations #10387General changes
startTransaction
API #9925Hub
class #11482Remove deprecated code
wrap
function #8897unblock
andunmask
will require explicit opt-in #8887_eventFromIncompleteOnError
is no longer required #5842configureScope
is used in a few templates sentry-wizard#519Docs
Other / open for discussion
?
and<anonymous>
to denote anonymous functions #5523ok
instead of none which leads tounknown
#5745startSpan
APIs #10772getTracingMetaTags
helper function to Node SDK #8843Testing
Check all SDKs for feature regression
ref #5194
ref #9802
The text was updated successfully, but these errors were encountered: