@sentry/vercel-edge

Internal Sentry Utilities for Vercel Edge Runtime

NOTICE: It is discouraged to depend on this package directly. @sentry/vercel-edge is used as building block for higher level Sentry SDKs like @sentry/nextjs. The API of this @sentry/vercel-edge may break with any major and non-major version!

Links

• Sentry.io
• Sentry Discord Server
• Stack Overflow

Changelog

9.14.0

Important Changes

• feat: Add Supabase Integration (#15719)

This PR adds Supabase integration to @sentry/core, allowing automatic instrumentation of Supabase client operations (database queries and authentication) for performance monitoring and error tracking.

• feat(nestjs): Gracefully handle RPC scenarios in SentryGlobalFilter (#16066)

This PR adds better RPC exception handling to @sentry/nestjs, preventing application crashes while still capturing errors and warning users when a dedicated filter is needed. The implementation gracefully handles the 'rpc' context type in SentryGlobalFilter to improve reliability in hybrid applications.

• feat(react-router): Trace propagation (#16070)

This PR adds trace propagation to @sentry/react-router by providing utilities to inject trace meta tags into HTML headers and offering a pre-built Sentry-instrumented request handler, improving distributed tracing capabilities across page loads.

Other Changes

• feat(deps): Bump @prisma/instrumentation from 6.5.0 to 6.6.0 (#16102)
• feat(nextjs): Improve server component data (#15996)
• feat(nuxt): Log when adding HTML trace meta tags (#16044)
• fix(node): Make body capturing more robust (#16105)
• ref(node): Log when incoming request bodies are being captured (#16104)