@sentry/vue
Advanced tools
Changelog
8.45.0
handled
option to captureConsoleIntegration
(#14664)HttpClient
events (#14515)captureMessage
with attachStacktrace: true
as synthetic (#14668)captureMessage
with attatchStackTrace: true
as synthetic (#14670)level
in server runtime captureException
(#10587)Work in this release was contributed by @anonrig and @Zih0. Thank you for your contributions!
Changelog
8.44.0
feat: Deprecate autoSessionTracking
(#14640)
Deprecates autoSessionTracking
.
To enable session tracking, it is recommended to unset autoSessionTracking
and ensure that either, in browser environments
the browserSessionIntegration
is added, or in server environments the httpIntegration
is added.
To disable session tracking, it is recommended to unset autoSessionTracking
and to remove the browserSessionIntegration
in
browser environments, or in server environments configure the httpIntegration
with the trackIncomingRequestsAsSessions
option set to false
.
response
context for http.server spans (#14634)Work in this release was contributed by @robinvw1. Thank you for your contribution!
Changelog
8.43.0
feat(nuxt): Add option autoInjectServerSentry (no default import()) (#14553)
Using the dynamic import()
as the default behavior for initializing the SDK on the server-side did not work for every project.
The default behavior of the SDK has been changed, and you now need to use the --import
flag to initialize Sentry on the server-side to leverage full functionality.
Example with --import
:
node --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs
In case you are not able to use the --import
flag, you can enable auto-injecting Sentry in the nuxt.config.ts
(comes with limitations):
sentry: {
autoInjectServerSentry: 'top-level-import', // or 'experimental_dynamic-import'
},
feat(browser): Adds LaunchDarkly and OpenFeature integrations (#14207)
Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:
import * as Sentry from '@sentry/browser';
Sentry.init({
integrations: [
// Track LaunchDarkly feature flags
Sentry.launchDarklyIntegration(),
// Track OpenFeature feature flags
Sentry.openFeatureIntegration(),
],
});
feat(browser): Add featureFlagsIntegration
for custom tracking of flag evaluations (#14582)
Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:
import * as Sentry from '@sentry/browser';
const featureFlagsIntegrationInstance = Sentry.featureFlagsIntegration();
Sentry.init({
// Initialize the SDK with the feature flag integration
integrations: [featureFlagsIntegrationInstance],
});
// Manually track a feature flag
featureFlagsIntegrationInstance.addFeatureFlag('my-feature', true);
feat(astro): Add Astro 5 support (#14613)
With this release, the Sentry Astro SDK officially supports Astro 5.
feat(nextjs): Deprecate typedef for hideSourceMaps
(#14594)
The functionality of hideSourceMaps
was removed in version 8 but was forgotten to be deprecated and removed.
It will be completely removed in the next major version.
feat(core): Deprecate APIs around RequestSession
s (#14566)
The APIs around RequestSession
s are mostly used internally.
Going forward the SDK will not expose concepts around RequestSession
s.
Instead, functionality around server-side Release Health will be managed in integrations.
browserSessionIntegration
(#14551)raw_security
envelope types (#14562)disableAnrDetectionForCallback
function (#14359)trackIncomingRequestsAsSessions
option to http integration (#14567)autoInjectServerSentry
(no default import()
) (#14553)^1.29.0
(#14590)1.28.0
(#14547)filename
and module
stack frame properties in Node stack parser (#14544)maxSpanWaitDuration
values (#14632)parseSearch
option in TanStack Router instrumentation (#14328)Work in this release was contributed by @lsmurray. Thank you for your contribution!
Changelog
8.42.0
feat(react): React Router v7 support (library) (#14513)
This release adds support for React Router v7 (library mode). Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs
feat: Warn about source-map generation (#14533)
In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application. Currently, the implementation varies a lot between different SDKs and can be difficult to understand. Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off. Additionally, if we end up enabling source maps, we will emit a log message that we did so.
With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.
feat(nuxt): Deprecate tracingOptions
in favor of vueIntegration
(#14530)
Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:
Sentry.init()
tracingOptions
in Sentry.init()
For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported vueIntegration()
and its tracingOptions
option to configure tracing options in the Nuxt SDK:
// sentry.client.config.ts
import * as Sentry from '@sentry/nuxt';
Sentry.init({
// ...
integrations: [
Sentry.vueIntegration({
tracingOptions: {
trackComponents: true,
},
}),
],
});