v7.50.0

Compare Source

Important Changes

• doc(sveltekit): Promote the SDK to beta state (#​7976)
  • feat(sveltekit): Convert sentryHandle to a factory function (#​7975)

With this release, the Sveltekit SDK (@​sentry/sveltekit) is promoted to Beta.
This means that we do not expect any more breaking changes.

The final breaking change is that sentryHandle is now a function.
So in order to update to 7.50.0, you have to update your hooks.server.js file:

// hooks.server.js

// Old:
export const handle = sentryHandle;
// New:
export const handle = sentryHandle();

• feat(replay): Allow to configure URLs to capture network bodies/headers (#​7953)

You can now capture request/response bodies & headers of network requests in Replay.
You have to define an allowlist of URLs you want to capture additional information for:

new Replay({
  networkDetailAllowUrls: ['https://sentry.io/api'],
});

By default, we will capture request/response bodies, as well as the request/response headers content-type, content-length and accept.
You can configure this with some additional configuration:

new Replay({
  networkDetailAllowUrls: ['https://sentry.io/api'],
  // opt-out of capturing bodies
  networkCaptureBodies: false,
  // These headers are captured _in addition to_ the default headers
  networkRequestHeaders: ['X-Custom-Header'],
  networkResponseHeaders: ['X-Custom-Header', 'X-Custom-Header-2']
});

Note that bodies will be truncated to a max length of ~150k characters.

- feat(replay): Changes of sampling behavior & public API

• feat(replay): Change the behavior of error-based sampling (#​7768)
• feat(replay): Change flush() API to record current event buffer (#​7743)
• feat(replay): Change stop() to flush and remove current session (#​7741)

We have changed the behavior of error-based sampling, as well as adding & adjusting APIs a bit to be more aligned with expectations.
See Sampling for details.

We've also revamped some public APIs in order to be better aligned with expectations. See Stoping & Starting Replays manually for details.

• feat(core): Add multiplexed transport (#​7926)

We added a new transport to support multiplexing.
With this, you can configure Sentry to send events to different DSNs, depending on a logic of your choosing:

import { makeMultiplexedTransport } from '@​sentry/core';
import { init, captureException, makeFetchTransport } from '@​sentry/browser';

function dsnFromFeature({ getEvent }) {
  const event = getEvent();
  switch(event?.tags?.feature) {
    case 'cart':
      return ['__CART_DSN__'];
    case 'gallery':
      return ['__GALLERY_DSN__'];
  }
  return []
}

init({
  dsn: '__FALLBACK_DSN__',
  transport: makeMultiplexedTransport(makeFetchTransport, dsnFromFeature)
});

Additional Features and Fixes

• feat(nextjs): Add disableLogger option that automatically tree shakes logger statements (#​7908)
• feat(node): Make Undici a default integration. (#​7967)
• feat(replay): Extend session idle time until expire to 15min (#​7955)
• feat(tracing): Add db.system span data to DB spans (#​7952)
• fix(core): Avoid crash when Function.prototype is frozen (#​7899)
• fix(nextjs): Fix inject logic for Next.js 13.3.1 canary (#​7921)
• fix(replay): Ensure console breadcrumb args are truncated (#​7917)
• fix(replay): Ensure we do not set replayId on dsc if replay is disabled (#​7939)
• fix(replay): Ensure we still truncate large bodies if they are failed JSON (#​7923)
• fix(utils): default normalize() to a max. of 100 levels deep instead of Inifnity (#​7957)

Work in this release contributed by @​Jack-Works. Thank you for your contribution!

v7.49.0

Compare Source

Important Changes

• feat(sveltekit): Read adapter output directory from svelte.config.js (#​7863)

Our source maps upload plugin is now able to read svelte.config.js. This is necessary to automatically find the output directory that users can specify when setting up the Node adapter.

• fix(replay): Ensure we normalize scope breadcrumbs to max. depth to avoid circular ref (#​7915)

This release fixes a potential problem with how Replay captures console logs.
Any objects logged will now be cut off after a maximum depth of 10, as well as cutting off any properties after the 1000th.
This should ensure we do not accidentally capture massive console logs, where a stringified object could reach 100MB or more.

• fix(utils): Normalize HTML elements as string (#​7916)

We used to normalize references to HTML elements as POJOs.
This is both not very easily understandable, as well as potentially large, as HTML elements may have properties attached to them.
With this change, we now normalize them to e.g. [HTMLElement: HTMLInputElement].

Additional Features and Fixes

• feat(browser): Simplify stack parsers (#​7897)
• feat(node): Add monitor upsert types (#​7914)
• feat(replay): Truncate network bodies to max size (#​7875)
• fix(gatsby): Don't crash build when auth token is missing (#​7858)
• fix(gatsby): Use import for gatsby-browser.js instead of require (#​7889)
• fix(nextjs): Handle braces in stack frame URLs (#​7900)
• fix(nextjs): Mark value injection loader result as uncacheable (#​7870)
• fix(node): Correct typo in trpc integration transaciton name (#​7871)
• fix(node): reduce deepReadDirSync runtime complexity (#​7910)
• fix(sveltekit): Avoid capturing "Not Found" errors in server handleError wrapper (#​7898)
• fix(sveltekit): Detect sentry release before creating the Vite plugins (#​7902)
• fix(sveltekit): Use sentry.properties file when uploading source maps (#​7890)
• fix(tracing): Ensure we use s instead of ms for startTimestamp (#​7877)
• ref(deprecate): Deprecate timestampWithMs (#​7878)
• ref(nextjs): Don't use Sentry Webpack Plugin in dev mode (#​7901)

v1.20.1

Compare Source

• fix: Update Webpack plugin to 1.75.1 to fix bug in Angular source maps (#​439)
• fix: Update @​sentry/cli to 1.75.0 to fix ansi-regex security warning (#​427)
• build(deps): bump loader-utils from 1.1.0 to 1.4.1 in /example