@sentry-internal/feedback

Sentry Integration for Feedback

This SDK is considered experimental and in a beta state. It may experience breaking changes, and may be discontinued at any time. Please reach out on GitHub if you have any feedback/concerns.

To view Feedback in Sentry, your Sentry organization must be an early adopter.

Installation

Please read the official integration documentation for installation instructions.

Configuration

The Feedback integration is highly customizable, please read the official integration documentation for the most up-to-date configuration options.

Changelog

9.32.0

Important Changes

• feat(browser): Add CLS sources to span attributes (#16710)

Enhances CLS (Cumulative Layout Shift) spans by adding attributes detailing the elements that caused layout shifts.

• feat(cloudflare): Add instrumentWorkflowWithSentry to instrument workflows (#16672)

We've added support for Cloudflare Workflows, enabling comprehensive tracing for your workflow runs. This integration uses the workflow's instanceId as the Sentry trace_id and for sampling, linking all steps together. You'll now be able to see full traces, including retries with exponential backoff.

• feat(pino-transport): Add functionality to send logs to sentry (#16667)

Adds the ability to send logs to Sentry via a pino transport.

Other Changes

• feat(nextjs): Expose top level buildTime errorHandler option (#16718)
• feat(node): update pipeline spans to use agent naming (#16712)
• feat(deps): bump @prisma/instrumentation from 6.9.0 to 6.10.1 (#16698)
• fix(sveltekit): Export logger from sveltekit worker (#16716)
• fix(google-cloud-serverless): Make CloudEventsContext compatible with CloudEvent (#16705)
• fix(nextjs): Stop injecting release value when create release options is set to false (#16695)
• fix(node): account for Object. syntax with local variables matching (#16702)
• fix(nuxt): Add alias for @opentelemetry/resources (#16727)

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