@sentry/tracing

Important Changes

• sveltekit: Read adapter output directory from svelte.config.js

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.

• replay: Ensure we normalize scope breadcrumbs to max. depth to avoid circular ref

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.

• utils: Normalize HTML elements as string

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

• browser: Simplify stack parsers

• node: Add monitor upsert types

• replay: Truncate network bodies to max size

• gatsby: Don't crash build when auth token is missing

• gatsby: Use import for gatsby-browser.js instead of require

• nextjs: Handle braces in stack frame URLs

• nextjs: Mark value injection loader result as uncacheable

• node: Reduce deepReadDirSync runtime complexity

• sveltekit: Avoid capturing "Not Found" errors in server handleError wrapper

• sveltekit: Detect sentry release before creating the Vite plugins

• sveltekit: Use sentry.properties file when uploading source maps

• tracing: Ensure we use s instead of ms for startTimestamp

• deprecated

  deprecate: Deprecate timestampWithMs

Bundle size