Update dependency @sentry/node to v7 - autoclosed #87

renovate · 2023-05-16T17:21:01Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/node (source)	`^6.17.4` -> `^7.73.0`

Release Notes

getsentry/sentry-javascript (@sentry/node)

`v7.73.0`

Compare Source

Important Changes

feat(replay): Upgrade to rrweb2

This is fully backwards compatible with prior versions of the Replay SDK. The only breaking change that we will making is to not be masking aria-label by default. The reason for this change is to align with our core SDK which also does not mask aria-label. This change also enables better support of searching by clicks.

Another change that needs to be highlighted is the 13% bundle size increase. This bundle size increase is necessary to bring improved recording performance and improved replay fidelity, especially in regards to web components and iframes. We will be investigating the reduction of the bundle size in this PR.

Here are benchmarks comparing the version 1 of rrweb to version 2

metric	v1	v2
lcp	1486.06 ms	1529.11 ms
cls	0.40 ms	0.40 ms
fid	1.53 ms	1.50 ms
tbt	3207.22 ms	3036.80 ms
memoryAvg	131.83 MB	124.84 MB
memoryMax	324.8 MB	339.03 MB
netTx	282.67 KB	272.51 KB
netRx	8.02 MB	8.07 MB

Other Changes

feat: Always assemble Envelopes (#9101)
feat(node): Rate limit local variables for caught exceptions and enable captureAllExceptions by default (#9102)
fix(core): Ensure tunnel is considered for isSentryUrl checks (#9130)
fix(nextjs): Fix RequestAsyncStorage fallback path (#9126)
fix(node-otel): Suppress tracing for generated sentry spans (#9142)
fix(node): fill in span data from http request options object (#9112)
fix(node): Fixes and improvements to ANR detection (#9128)
fix(sveltekit): Avoid data invalidation in wrapped client-side load functions (#9071)
ref(core): Refactor InboundFilters integration to use processEvent (#9020)
ref(wasm): Refactor Wasm integration to use processEvent (#9019)

Work in this release contributed by @vlad-zhukov. Thank you for your contribution!

Bundle size 📦

Path	Size
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	84.26 KB
@sentry/browser (incl. Tracing) - Webpack (gzipped)	31.42 KB
@sentry/browser - Webpack (gzipped)	22 KB
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	78.69 KB
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.52 KB
@sentry/browser - ES6 CDN Bundle (gzipped)	20.59 KB
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	254.14 KB
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	86.42 KB
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	61.23 KB
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	31.38 KB
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	84.28 KB
@sentry/react - Webpack (gzipped)	22.03 KB
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	102.2 KB
@sentry/nextjs Client - Webpack (gzipped)	50.95 KB

`v7.72.0`

Compare Source

Important Changes

feat(node): App Not Responding with stack traces (#9079)

This release introduces support for Application Not Responding (ANR) errors for Node.js applications.
These errors are triggered when the Node.js main thread event loop of an application is blocked for more than five seconds.
The Node SDK reports ANR errors as Sentry events and can optionally attach a stacktrace of the blocking code to the ANR event.

To enable ANR detection, import and use the enableANRDetection function from the @sentry/node package before you run the rest of your application code.
Any event loop blocking before calling enableANRDetection will not be detected by the SDK.

Example (ESM):

import * as Sentry from "@&#8203;sentry/node";

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  tracesSampleRate: 1.0,
});

await Sentry.enableANRDetection({ captureStackTrace: true });
// Function that runs your app
runApp();

Example (CJS):

const Sentry = require("@&#8203;sentry/node");

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  tracesSampleRate: 1.0,
});

Sentry.enableANRDetection({ captureStackTrace: true }).then(() => {
  // Function that runs your app
  runApp();
});

Other Changes

fix(nextjs): Filter RequestAsyncStorage locations by locations that webpack will resolve (#9114)
fix(replay): Ensure replay_id is not captured when session is expired (#9109)

`v7.71.0`

Compare Source

feat(bun): Instrument Bun.serve (#9080)
fix(core): Ensure global event processors are always applied to event (#9064)
fix(core): Run client eventProcessors before global ones (#9032)
fix(nextjs): Use webpack module paths to attempt to resolve internal request async storage module (#9100)
fix(react): Add actual error name to boundary error name (#9065)
fix(react): Compare location against basename-prefixed route. (#9076)
ref(browser): Refactor browser integrations to use processEvent (#9022)

Work in this release contributed by @jorrit. Thank you for your contribution!

`v7.70.0`

Compare Source

Important Changes

feat: Add Bun SDK (#9029)

This release contains the beta version of @sentry/bun, our SDK for the Bun JavaScript runtime! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

Note that as of now the Bun runtime does not support global error handlers. This is being actively worked on, see the tracking issue in Bun's GitHub repo.

feat(remix): Add Remix 2.x release support. (#8940)

The Sentry Remix SDK now officially supports Remix v2! See our Remix docs for more details.

Other Changes

chore(node): Upgrade cookie to ^0.5.0 (#9013)
feat(core): Introduce processEvent hook on Integration (#9017)
feat(node): Improve non-error messages (#9026)
feat(vercel-edge): Add Vercel Edge Runtime package (#9041)
fix(remix): Use React.ComponentType instead of React.FC as withSentry's generic type. (#9043)
fix(replay): Ensure replay events go through preprocessEvent hook (#9034)
fix(replay): Fix typo in Replay types (#9028)
fix(sveltekit): Adjust handleErrorWithSentry type (#9054)
fix(utils): Try-catch monkeypatching to handle frozen objects/functions (#9031)

Work in this release contributed by @Dima-Dim, @krist7599555 and @lifeiscontent. Thank you for your contributions!

Special thanks for @isaacharrisholt for helping us implement a Vercel Edge Runtime SDK which we use under the hood for our Next.js SDK.

Bundle size 📦

Path	Size
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	75.58 KB
@sentry/browser (incl. Tracing) - Webpack (gzipped)	31.49 KB
@sentry/browser - Webpack (gzipped)	22.09 KB
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	70.27 KB
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.59 KB
@sentry/browser - ES6 CDN Bundle (gzipped)	20.66 KB
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	222.15 KB
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	86.64 KB
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	61.49 KB
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	31.46 KB
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	75.61 KB
@sentry/react - Webpack (gzipped)	22.12 KB
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	93.49 KB
@sentry/nextjs Client - Webpack (gzipped)	51.07 KB

`v7.69.0`

Compare Source

Important Changes

New Performance APIs
- feat: Update span performance API names (#8971)
- feat(core): Introduce startSpanManual (#8913)

This release introduces a new set of top level APIs for the Performance Monitoring SDKs. These aim to simplify creating spans and reduce the boilerplate needed for performance instrumentation. The three new methods introduced are Sentry.startSpan, Sentry.startInactiveSpan, and Sentry.startSpanManual. These methods are available in the browser and node SDKs.

Sentry.startSpan wraps a callback in a span. The span is automatically finished when the callback returns. This is the recommended way to create spans.

// Start a span that tracks the duration of expensiveFunction
const result = Sentry.startSpan({ name: 'important function' }, () => {
  return expensiveFunction();
});

// You can also mutate the span wrapping the callback to set data or status
Sentry.startSpan({ name: 'important function' }, (span) => {
  // span is undefined if performance monitoring is turned off or if
  // the span was not sampled. This is done to reduce overhead.
  span?.setData('version', '1.0.0');
  return expensiveFunction();
});

If you don't want the span to finish when the callback returns, use Sentry.startSpanManual to control when the span is finished. This is useful for event emitters or similar.

// Start a span that tracks the duration of middleware
function middleware(_req, res, next) {
  return Sentry.startSpanManual({ name: 'middleware' }, (span, finish) => {
    res.once('finish', () => {
      span?.setHttpStatus(res.status);
      finish();
    });
    return next();
  });
}

Sentry.startSpan and Sentry.startSpanManual create a span and make it active for the duration of the callback. Any spans created while this active span is running will be added as a child span to it. If you want to create a span without making it active, use Sentry.startInactiveSpan. This is useful for creating parallel spans that are not related to each other.

const span1 = Sentry.startInactiveSpan({ name: 'span1' });

someWork();

const span2 = Sentry.startInactiveSpan({ name: 'span2' });

moreWork();

const span3 = Sentry.startInactiveSpan({ name: 'span3' });

evenMoreWork();

span1?.finish();
span2?.finish();
span3?.finish();

Other Changes

feat(core): Export BeforeFinishCallback type (#8999)
build(eslint): Enforce that ts-expect-error is used (#8987)
feat(integration): Ensure LinkedErrors integration runs before all event processors (#8956)
feat(node-experimental): Keep breadcrumbs on transaction (#8967)
feat(redux): Add 'attachReduxState' option (#8953)
feat(remix): Accept org, project and url as args to upload script (#8985)
fix(utils): Prevent iterating over VueViewModel (#8981)
fix(utils): uuidv4 fix for cloudflare (#8968)
fix(core): Always use event message and exception values for ignoreErrors (#8986)
fix(nextjs): Add new potential location for Next.js request AsyncLocalStorage (#9006)
fix(node-experimental): Ensure we only create HTTP spans when outgoing (#8966)
fix(node-experimental): Ignore OPTIONS & HEAD requests (#9001)
fix(node-experimental): Ignore outgoing Sentry requests (#8994)
fix(node-experimental): Require parent span for pg spans (#8993)
fix(node-experimental): Use Sentry logger as Otel logger (#8960)
fix(node-otel): Refactor OTEL span reference cleanup (#9000)
fix(react): Switch to props in useRoutes (#8998)
fix(remix): Add glob to Remix SDK dependencies. (#8963)
fix(replay): Ensure handleRecordingEmit aborts when event is not added (#8938)
fix(replay): Fully stop & restart session when it expires (#8834)

Work in this release contributed by @Duncanxyz and @malay44. Thank you for your contributions!

`v7.68.0`

Compare Source

feat(browser): Add BroadcastChannel and SharedWorker to TryCatch EventTargets (#8943)
feat(core): Add name to Span (#8949)
feat(core): Add ServerRuntimeClient (#8930)
fix(node-experimental): Ensure span.finish() works as expected (#8947)
fix(remix): Add new sourcemap-upload script files to prepack assets. (#8948)
fix(publish): Publish downleveled TS3.8 types and fix types path (#8954)

`v7.67.0`

Compare Source

Important Changes

feat: Mark errors caught by the SDK as unhandled
- feat(browser): Mark errors caught from TryCatch integration as unhandled (#8890)
- feat(integrations): Mark errors caught from HttpClient and CaptureConsole integrations as unhandled (#8891)
- feat(nextjs): Mark errors caught from NextJS wrappers as unhandled (#8893)
- feat(react): Mark errors captured from ErrorBoundary as unhandled (#8914)
- feat(remix): Add debugid injection and map deletion to sourcemaps script (#8814)
- feat(remix): Mark errors caught from Remix instrumentation as unhandled (#8894)
- feat(serverless): Mark errors caught in Serverless handlers as unhandled (#8907)
- feat(vue): Mark errors caught by Vue wrappers as unhandled (#8905)

This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled.
Previously, some of our instrumentations correctly set unhandled, while others set handled.
Going forward, all errors caught automatically from our SDKs will be marked as unhandled.
If you manually capture errors (e.g. by calling Sentry.captureException), your errors will continue to be reported as handled.

This change might lead to a decrease in reported crash-free sessions and consequently in your release health score.
If you have concerns about this, feel free to open an issue.

Other Changes

feat(node-experimental): Implement new performance APIs (#8911)
feat(node-experimental): Sync OTEL context with Sentry AsyncContext (#8797)
feat(replay): Allow to configure maxReplayDuration (#8769)
fix(browser): Add replay and profiling options to BrowserClientOptions (#8921)
fix(browser): Check for existence of instrumentation targets (#8939)
fix(nextjs): Don't re-export default in route handlers (#8924)
fix(node): Improve mysql integration (#8923)
fix(remix): Guard against missing default export for server instrument (#8909)
ref(browser): Deprecate top-level wrap function (#8927)
ref(node-otel): Avoid exporting internals & refactor attribute adding (#8920)

Work in this release contributed by @SorsOps. Thank you for your contribution!

`v7.66.0`

Compare Source

fix: Defer tracing decision to downstream SDKs when using SDK without performance (#8839)
fix(nextjs): Fix package.json exports (#8895)
fix(sveltekit): Ensure target file exists before applying auto instrumentation (#8881)
ref: Use consistent console instrumentation (#8879)
ref(browser): Refactor sentry breadcrumb to use hook (#8892)
ref(tracing): Add origin to spans (#8765)

`v7.65.0`

Compare Source

build: Remove build-specific polyfills (#8809)
build(deps): bump protobufjs from 6.11.3 to 6.11.4 (#8822)
deps(sveltekit): Bump @sentry/vite-plugin (#8877)
feat(core): Introduce Sentry.startActiveSpan and Sentry.startSpan (#8803)
fix: Memoize AsyncLocalStorage instance (#8831)
fix(nextjs): Check for validity of API route handler signature (#8811)
fix(nextjs): Fix requestAsyncStorageShim path resolution on windows (#8875)
fix(node): Log entire error object in OnUncaughtException (#8876)
fix(node): More relevant warning message when tracing extensions are missing (#8820)
fix(replay): Streamline session creation/refresh (#8813)
fix(sveltekit): Avoid invalidating data on route changes in wrapServerLoadWithSentry (#8801)
fix(tracing): Better guarding for performance observer (#8872)
ref(sveltekit): Remove custom client fetch instrumentation and use default instrumentation (#8802)
ref(tracing-internal): Deprecate tracePropagationTargets in BrowserTracing (#8874)

`v7.64.0`

Compare Source

feat(core): Add setMeasurement export (#8791)
fix(nextjs): Check for existence of default export when wrapping pages (#8794)
fix(nextjs): Ensure imports are valid relative paths (#8799)
fix(nextjs): Only re-export default export if it exists (#8800)

`v7.63.0`

Compare Source

build(deps): bump @opentelemetry/instrumentation from 0.41.0 to 0.41.2
feat(eventbuilder): Export exceptionFromError for use in hybrid SDKs (#8766)
feat(node-experimental): Re-export from node (#8786)
feat(tracing): Add db connection attributes for mysql spans (#8775)
feat(tracing): Add db connection attributes for postgres spans (#8778)
feat(tracing): Improve data collection for mongodb spans (#8774)
fix(nextjs): Execute sentry config independently of autoInstrumentServerFunctions and autoInstrumentAppDirectory (#8781)
fix(replay): Ensure we do not flush if flush took too long (#8784)
fix(replay): Ensure we do not try to flush when we force stop replay (#8783)
fix(replay): Fix hasCheckout handling (#8782)
fix(replay): Handle multiple clicks in a short time (#8773)
ref(replay): Skip events being added too long after initial segment (#8768)

`v7.62.0`

Compare Source

Important Changes

feat(integrations): Add ContextLines integration for html-embedded JS stack frames (#8699)

This release adds the ContextLines integration as an optional integration for the Browser SDKs to @sentry/integrations.

This integration adds source code from inline JavaScript of the current page's HTML (e.g. JS in <script> tags) to stack traces of captured errors.
It can't collect source code from assets referenced by your HTML (e.g. <script src="..." />).

The ContextLines integration is useful when you have inline JS code in HTML pages that can't be accessed by Sentry's backend, for example, due to a login-protected page.

import { ContextLines } from "@&#8203;sentry/integrations";

Sentry.init({
  // ...
  integrations: [
    new ContextLines({
      // The number of lines to collect before and after each stack frame's line number
      // Defaults to 7
      frameContextLines: 7,
    }),
  ],
});

Other Changes

fix(nextjs): Make all wrappers isomorphic and available in all runtimes (#8743)
fix(replay): Cancel debounce when replay is too short/long (#8742)
fix(utils): dirname and basename should handle Windows paths (#8737)
ref: Hoist flush, close, and lastEventId into @sentry/core (#8731)
ref(node): Don't call JSON.stringify on prisma client when logging (#8745)

`v7.61.1`

Compare Source

feat(nextjs): Add AsyncLocalStorage async context strategy to edge SDK (#8720)
fix(core): Filter internal API frames for synthetic frames (#8710)
fix(integrations): Capture exception if any arg to console method is an error (#8671)
fix(node-experimental): Update auto integration lookup & readme (#8690)
fix(node): Add availablility check on current hub to Node ContextLines integration (#8715)
fix(replay): Ensure buffer sessions end after capturing an error (#8713)
fix(replay): Ensure buffer->session switch is reliable (#8712)
fix(replay): Ensure we debounce flush if replay too short (#8716)
fix(replay): Improve capture of errorIds/traceIds (#8678)
fix(tracing): Set correct parent span id on fetch sentry-trace header (#8687)
fix(utils): Avoid pre_context and context_line overlap if frame lineno is out of bounds (#8722)
ref(replay): Improve status logging (#8709)
ref(nextjs): Allow withSentryConfig to accept async config function (#8721)

`v7.61.0`

Compare Source

Important Changes

feat(node-experimental): Add @sentry/node-experimental package as MVP for POTEL (#8609)

This introduces a new, experimental package, @sentry/node-experimental.
This is a variant of the Node SDK which uses OpenTelemetry under the hood for performance instrumentation.

Note that this package is very much WIP, considered unstable and may change at any time.
No SemVer guarantees apply whatsoever. Still, if you're brave enough you can give it a try.
Read more about @sentry/node-experimental

Other Changes

fix(node): Don't set extra baggage headers (#8657)
fix(tracing): Trim idle transaction spans if they exceed final timeout (#8653)

`v7.60.1`

Compare Source

fix(nextjs): Match folder paths with trailing separator (#8615)
fix(replay): Ignore clicks with shift pressed (#8648)
fix(replay): Use session.started for min/max duration check (#8617)

`v7.60.0`

Compare Source

Important Changes

feat(replay): Ensure min/max duration when flushing (#8596)

We will not send replays that are <5s long anymore. Additionally, we also added further safeguards to avoid overly long (>1h) replays.
You can optionally configure the min. replay duration (defaults to 5s):

new Replay({
  minReplayDuration: 10000 // in ms - note that this is capped at 15s max!
})

Other Changes

fix(profiling): Align to SDK selected time origin (#8599)
fix(replay): Ensure multi click has correct timestamps (#8591)
fix(utils): Truncate aggregate exception values (LinkedErrors) (#8593)

`v7.59.3`

Compare Source

fix(browser): 0 is a valid index (#8581)
fix(nextjs): Ensure Webpack plugin is available after dynamic require (#8584)
types(browser): Add browser profiling client options (#8565)

`v7.59.2`

Compare Source

No changes. This release was published to fix publishing issues with 7.59.0 and 7.59.1.
Please see 7.59.0 for the changes in that release.

`v7.59.1`

Compare Source

No changes. This release was published to fix a publishing issue with 7.59.0.
Please see 7.59.0 for the changes in that release.

`v7.58.1`

Compare Source

fix(node): Set propagation context even when tracingOptions are not defined (#8517)

`v7.58.0`

Compare Source

Important Changes

Performance Monitoring not required for Distributed Tracing

This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the tracePropagationTargets option, which controls what requests to attach the sentry-trace and baggage HTTP headers to (which is what propagates tracing information).

Sentry.init({
  tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/],
});

feat(tracing): Add tracing without performance to browser and client Sveltekit (#8458)
feat(node): Add tracing without performance to Node http integration (#8450)
feat(node): Add tracing without performance to Node Undici (#8449)
feat(node): Populate propagation context using env variables (#8422)
feat(core): Support AggregateErrors in LinkedErrors integration (#8463)

This release adds support for AggregateErrors. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.

Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.

feat(replay): Add a new option networkDetailDenyUrls (#8439)

This release adds a new option networkDetailDenyUrls to the Replay integration. This option allows you to specify a list of URLs that should not be captured by the Replay integration, which can be used alongside the existing networkDetailAllowUrls for finely grained control of which URLs should have network details captured.

Sentry.init({
  integrations: [
    new Sentry.Integrations.Replay({
      networkDetailDenyUrls: [/^http:\/\/example.com\/test$/],
    }),
  ],
});

Other Changes

feat(core): Add helpers to get module metadata from injected code (#8438)
feat(core): Add sampling decision to trace envelope header (#8483)
feat(node): Add trace context to checkin (#8503)
feat(node): Export getModule for Electron SDK (#8488)
feat(types): Allow user.id to be a number (#8330)
fix(browser): Set anonymous crossorigin attribute on report dialog (#8424)
fix(nextjs): Ignore tunnelRoute when doing static exports (#8471)
fix(nextjs): Use basePath option for tunnelRoute (#8454)
fix(node): Apply source context to linked errors even when it is uncached (#8453)
fix(node): report errorMiddleware errors as unhandled (#8048)
fix(react): Add support for basename option of createBrowserRouter (#8457)
fix(remix): Add explicit @sentry/node exports. (#8509)
fix(remix): Don't inject trace/baggage to redirect and catch responses (#8467)
fix(replay): Adjust slow/multi click handling (#8380)

Work in this release contributed by @mrdulin, @donaldxdonald & @ziyad-elabid-nw. Thank you for your contributions!

`v7.57.0`

Compare Source

Important Changes

build: Update typescript from 3.8.3 to 4.9.5 (#8255)

This release version bumps the internally used typescript version from 3.8.x to 4.9.x.
We use ds-downlevel to generate two versions of our types, one for >=3.8, one for >=4.9.
This means that this change should be fully backwards compatible and not have any noticable user impact,
but if you still encounter issues please let us know.

feat(types): Add tracePropagationTargets to top level options (#8395)

Instead of passing tracePropagationTargets to the BrowserTracing integration, you can now define them on the top level:

Sentry.init({
  tracePropagationTargets: ['api.site.com'],
});

fix(angular): Filter out TryCatch integration by default (#8367)

The Angular and Angular-ivy SDKs will not install the TryCatch integration anymore by default.
This integration conflicted with the SentryErrorHander, sometimes leading to duplicated errors and/or missing data on events.

feat(browser): Better event name handling for non-Error objects (#8374)

When capturing non-errors via Sentry.captureException(), e.g. Sentry.captureException({ prop: "custom object" }),
we now generate a more helpful value for the synthetic exception. Instead of e.g. Non-Error exception captured with keys: currentTarget, isTrusted, target, type, you'll now get messages like:

Object captured as exception with keys: prop1, prop2
Event `MouseEvent` (type=click) captured as exception
Event `ErrorEvent` captured as exception with message `Script error.`

Other Changes

feat(browser): Send profiles in same envelope as transactions (#8375)
feat(profiling): Collect timings on profiler stop calls (#8409)
feat(replay): Do not capture replays < 5 seconds (GA) (#8277)
feat(tracing): Add experiment to capture http timings (#8371)
feat(tracing): Add http.response.status_code to span.data (#8366)
fix(angular): Stop routing spans on navigation cancel and error events (#8369)
fix(core): Only start spans in trace if tracing is enabled (#8357)
fix(nextjs): Inject init calls via loader instead of via entrypoints (#8368)
fix(replay): Mark ui.slowClickDetected clickCount as optional (#8376)
fix(serverless): Export autoDiscoverNodePerformanceMonitoringIntegrations from SDK (#8382)
fix(sveltekit): Check for cached requests in client-side fetch instrumentation (#8391)
fix(sveltekit): Only instrument SvelteKit fetch if the SDK client is valid (#8381)
fix(tracing): Instrument Prisma client in constructor of integration (#8383)
ref(replay): More graceful sessionStorage check (#8394)
ref(replay): Remove circular dep in replay eventBuffer (#8389)

`v7.56.0`

Compare Source

feat(replay): Rework slow click & multi click detection (#8322)
feat(replay): Stop replay when event buffer exceeds max. size (#8315)
feat(replay): Consider window.open for slow clicks (#8308)
fix(core): Temporarily store debug IDs in stack frame and only put them into debug_meta before sending (#8347)
fix(remix): Extract deferred responses correctly in root loaders. (#8305)
fix(vue): Don't call next in Vue router 4 instrumentation (#8351)

`v7.55.2`

Compare Source

fix(replay): Stop exporting EventType from @sentry-internal/rrweb (#8334)
fix(serverless): Export captureCheckIn (#8333)

`v7.55.1`

Compare Source

fix(replay): Do not export types from @sentry-internal/rrweb (#8329)

`v7.55.0`

Compare Source

feat(replay): Capture slow clicks (GA) (#8298)
feat(replay): Improve types for replay recording events (#8224)
fix(nextjs): Strip query params from transaction names of navigations to unknown routes (#8278)
fix(replay): Ignore max session life for buffered sessions (#8258)
fix(sveltekit): Export captureCheckIn (#8313)
ref(svelte): Add Svelte 4 as a peer dependency (#8280)

`v7.54.0`

Compare Source

Important Changes

feat(core): Add default entries to ignoreTransactions for Healthchecks #8191

All SDKs now filter out health check transactions by default.
These are transactions where the transaction name matches typical API health check calls, such as /^.*healthy.*$/ or /^. *heartbeat.*$/. Take a look at this list to learn which regexes we currently use to match transaction names.
We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default.
These filters are implemented as default values for the top level ignoreTransactions option.

You can disable this filtering by manually specifiying the InboundFilters integration and setting the disableTransactionDefaults option:
```
Sentry.init({
  //...
  integrations: [new InboundFilters({ disableTransactionDefaults: true })],
})
```
feat(replay): Add mutationBreadcrumbLimit and mutationLimit to Replay Options (#8228)

The previously experimental options mutationBreadcumbLimit and mutationLimit have been promoted to regular Replay integration options.

A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers.
Use mutationBreadcrumbLimit to send a breadcrumb along with your recording if the mutation limit was reached.
Use mutationLimit to stop recording if the mutation limit was reached.
feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)
- feat(sveltekit): Auto-detect SvelteKit adapters (#8193)
The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel.
By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary.
If you want to override the default adapter detection, you can specify the adapter option in the sentrySvelteKit options:
```
// vite.config.js
export default defineConfig({
  plugins: [
    sentrySvelteKit({
      adapter: 'vercel',
    }),
    sveltekit(),
  ],
});
```
Currently, the Vite plugin will configure itself correctly for @sveltejs/adapter-auto, @sveltejs/adapter-vercel and @sveltejs/adapter-node.

Important: The SvelteKit SDK is not yet compatible with Vercel's edge runtime.
It will only work for lambda functions.

Other Changes

feat(replay): Throttle breadcrumbs to max 300/5s (#8086)
feat(sveltekit): Add option to control handling of unknown server routes (#8201)
fix(node): Strip query and fragment from request URLs without route parameters (#8213)
fix(remix): Don't log missing parameters warning on server-side. (#8269)
fix(remix): Pass loadContext through wrapped document request function (#8268)
fix(replay): Guard against missing key (#8246)
fix(sveltekit): Avoid capturing redirects and 4xx Http errors in request Handlers (#8215)
fix(sveltekit): Bump magicast to support satisfied keyword (#8254)
fix(wasm): Avoid throwing an error when WASM modules are loaded from blobs (#8263)

`v7.53.1`

Compare Source

chore(deps): bump socket.io-parser from 4.2.1 to 4.2.3 (#8196)
chore(svelte): Bump magic-string to 0.30.0 (#8197)
fix(core): Fix racecondition that modifies in-flight sessions (#8203)
fix(node): Catch os.uptime() throwing because of EPERM (#8206)
fix(replay): Fix buffered replays creating replay w/o error occuring (#8168)

`v7.53.0`

Compare Source

feat(replay): Add beforeAddRecordingEvent Replay option (#8124)
feat(replay): Do not capture replays < 5 seconds (#7949)
fix(nextjs): Guard for non-absolute paths when injecting sentry config (#8151)
fix(nextjs): Import path issue on Windows (#8142)
fix(nextjs): Make withSentryConfig isomorphic (#8166)
fix(node): Add debug logging for node checkin (#8131)
fix(node): Add LRU map for tracePropagationTargets calculation (#8130)
fix(node): Remove new URL usage in Undici integration (#8147)
fix(replay): Show the correct Replay config option name maskFn
fix(sveltekit): Avoid double-wrapping load functions (#8094)
fix(tracing): Change where content-length gets added (#8139)
fix(tracing): Use integer for content length ([#8152](https://togithub.com/getsentry/sentry-javascript/issues/8

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate bot requested a review from nguyenchr as a code owner May 16, 2023 17:21

renovate bot force-pushed the renovate/sentry-node-7.x branch 2 times, most recently from 003e216 to b5981ad Compare May 24, 2023 17:41

renovate bot force-pushed the renovate/sentry-node-7.x branch from b5981ad to 1c9ca5e Compare June 2, 2023 05:07

renovate bot force-pushed the renovate/sentry-node-7.x branch 2 times, most recently from 10192eb to 56d232a Compare June 20, 2023 23:57

renovate bot force-pushed the renovate/sentry-node-7.x branch from 56d232a to f02d49a Compare June 29, 2023 05:59

renovate bot force-pushed the renovate/sentry-node-7.x branch 3 times, most recently from 4264b84 to 576c4ba Compare July 19, 2023 20:53

renovate bot force-pushed the renovate/sentry-node-7.x branch 2 times, most recently from 2c6fbbf to e5eef42 Compare July 27, 2023 05:30

renovate bot force-pushed the renovate/sentry-node-7.x branch 2 times, most recently from 747c2a9 to fe4a3e1 Compare August 4, 2023 14:42

renovate bot force-pushed the renovate/sentry-node-7.x branch 2 times, most recently from 9eb9cf8 to 43d63e3 Compare August 15, 2023 11:42

renovate bot force-pushed the renovate/sentry-node-7.x branch 2 times, most recently from 2646423 to ea6e704 Compare August 31, 2023 02:22

renovate bot force-pushed the renovate/sentry-node-7.x branch from ea6e704 to 2aa9b99 Compare September 6, 2023 23:31

renovate bot force-pushed the renovate/sentry-node-7.x branch 2 times, most recently from dc0f765 to 1b494e7 Compare September 21, 2023 05:22

renovate bot force-pushed the renovate/sentry-node-7.x branch 2 times, most recently from 4712c76 to 27821f8 Compare September 27, 2023 02:33

Update dependency @sentry/node to v7

d490595

renovate bot force-pushed the renovate/sentry-node-7.x branch from 27821f8 to d490595 Compare October 3, 2023 02:15

renovate bot changed the title ~~Update dependency @sentry/node to v7~~ Update dependency @sentry/node to v7 - autoclosed Oct 6, 2023

renovate bot closed this Oct 6, 2023

renovate bot deleted the renovate/sentry-node-7.x branch October 6, 2023 05:50

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency @sentry/node to v7 - autoclosed #87

Update dependency @sentry/node to v7 - autoclosed #87

renovate bot commented May 16, 2023 •

edited

Loading

Update dependency @sentry/node to v7 - autoclosed #87

Update dependency @sentry/node to v7 - autoclosed #87

Conversation

renovate bot commented May 16, 2023 • edited Loading

Release Notes

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Configuration

renovate bot commented May 16, 2023 •

edited

Loading