Update dependency @sentry/node to v8.35.0
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
@sentry/node (source) | dependencies | minor | 8.33.1 -> 8.35.0 |
Release Notes
getsentry/sentry-javascript (@sentry/node)
v8.35.0
Beta release of the official Nuxt Sentry SDK
This release marks the beta release of the @sentry/nuxt
Sentry SDK. For details on how to use it, check out the
Sentry Nuxt SDK README. Please reach out on
GitHub if you have any feedback or concerns.
- feat(nuxt): Make dynamic import() wrapping default (#13958) (BREAKING)
- feat(nuxt): Add Rollup plugin to wrap server entry with
import()
(#13945)
It is no longer required to add a Node --import
flag. Please update your start command to avoid initializing Sentry
twice (BREAKING CHANGE). The SDK will now apply modifications during the build of your application to allow for
patching of libraries during runtime. If run into issues with this change, you can disable this behavior in your
nuxt.config.ts
and use the --import
flag instead:
sentry: {
dynamicImportForServerEntry: false;
}
- feat(nuxt): Respect user-provided source map generation settings (#14020)
We now require you to explicitly enable sourcemaps for the clientside so that Sentry can un-minify your errors. We made this change so source maps aren't accidentally leaked to the public. Enable source maps on the client as follows:
export default defineNuxtConfig({
sourcemap: {
client: true,
},
});
- feat(nuxt): Log server instrumentation might not work in dev (#14021)
- feat(nuxt): Add Http
responseHook
withwaitUntil
(#13986)
Important Changes
- feat(vue): Add Pinia plugin (#13841)
Support for Pinia is added in this release for @sentry/vue
. To capture Pinia state data,
add createSentryPiniaPlugin()
to your Pinia store:
import { createPinia } from 'pinia';
import { createSentryPiniaPlugin } from '@​sentry/vue';
const pinia = createPinia();
pinia.use(createSentryPiniaPlugin());
- feat(node): Implement Sentry-specific http instrumentation (#13763)
This change introduces a new SentryHttpInstrumentation
to handle non-span related HTTP instrumentation, allowing it to
run side-by-side with OTel's HttpInstrumentation
. This improves support for custom OTel setups and avoids conflicts
with Sentry's instrumentation. Additionally, the spans: false
option is reintroduced for httpIntegration
to disable
span emission while still allowing custom HttpInstrumentation
instances (httpIntegration({ spans: false })
).
- feat(core): Make stream instrumentation opt-in (#13951)
This change adds a new option trackFetchStreamPerformance
to the browser tracing integration. Only when set to true
,
Sentry will instrument streams via fetch.
Other Changes
- feat(node): Expose
suppressTracing
API (#13875) - feat(replay): Do not log "timeout while trying to read resp body" as exception (#13965)
- chore(node): Bump
@opentelemetry/instrumentation-express
to0.43.0
(#13948) - chore(node): Bump
@opentelemetry/instrumentation-fastify
to0.40.0
(#13983) - fix: Ensure type for
init
is correct in meta frameworks (#13938) - fix(core):
.set
thesentry-trace
header instead of.append
ing in fetch instrumentation (#13907) - fix(module): keep version for node ESM package (#13922)
- fix(node): Ensure
ignoreOutgoingRequests
ofhttpIntegration
applies to breadcrumbs (#13970) - fix(replay): Fix onError sampling when loading an expired buffered session (#13962)
- fix(replay): Ignore older performance entries when starting manually (#13969)
- perf(node): Truncate breadcrumb messages created by console integration (#14006)
Work in this release was contributed by @ZakrepaShe and @zhiyan114. Thank you for your contributions!
v8.34.0
Important Changes
- ref(nextjs): Remove dead code (#13828)
Relevant for users of the @sentry/nextjs
package: If you have previously configured a
SENTRY_IGNORE_API_RESOLUTION_ERROR
environment variable, it is now safe to unset it.
Other Changes
- feat(cdn): Export
getReplay
in replay CDN bundles (#13881) - feat(replay): Clear fallback buffer when switching buffers (#13914)
- feat(replay): Upgrade rrweb packages to 2.28.0 (#13732)
- fix(docs): Correct supported browsers due to
globalThis
(#13788) - fix(nextjs): Adjust path to
requestAsyncStorageShim.js
template file (#13928) - fix(nextjs): Detect new locations for request async storage to support Next.js v15.0.0-canary.180 and higher (#13920)
- fix(nextjs): Drop
_not-found
spans for all HTTP methods (#13906) - fix(nextjs): Fix resolution of request storage shim fallback (#13929)
- fix(node): Ensure graphql options are correct when preloading (#13769)
- fix(node): Local variables handle error (#13827)
- fix(node): Remove
dataloader
instrumentation from default integrations (#13873) - fix(nuxt): Create declaration files for Nuxt module (#13909)
- fix(replay): Ensure
replay_id
is removed from frozen DSC when stopped (#13893) - fix(replay): Try/catch
sendBufferedReplayOrFlush
to prevent cycles (#13900) - fix(sveltekit): Ensure trace meta tags are always injected (#13231)
- fix(sveltekit): Update
wrapServerRouteWithSentry
to respect ParamMatchers (#13390) - fix(wasm): Integration wasm uncaught WebAssembly.Exception (#13787) (#13854)
- ref(nextjs): Ignore sentry spans based on query param attribute (#13905)
- ref(utils): Move
vercelWaitUntil
to utils (#13891)
Work in this release was contributed by @trzeciak, @gurpreetatwal, @ykzts and @lizhiyao. Thank you for your contributions!
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.