@sentry/ember

This release adds an environment check in @sentry/nextjs for Vercel deployments (using the VERCEL_ENV env variable), and only enables SentryWebpackPlugin if the environment is production. To override this, setting disableClientWebpackPlugin or disableServerWebpackPlugin to false now takes precedence over other checks, rather than being a no-op. Note: Overriding this is not recommended! It can increase build time and clog Release Health data in Sentry with inaccurate noise.

• browser: Use valid urls in Request checks

• integrations: Don't add empty stack trace in RewriteFrames

• nextjs: Create transactions in getInitialProps and getServerSideProps

• nextjs: Instrument server-side getInitialProps of _app, _document and _error

• nextjs: Start navigation transactions on same-route navigations

• nextjs: Don't run webpack plugin on non-prod Vercel deployments

• node: Populate event.contexts for Node.js

• node: Avoid catching domain errors in request handler

• serverless: Check for existence of callback in GCP event handler before calling

• svelte: Add Component Tracking

Work in this release contributed by @lucas-zimerman, @GJZwiers, and @mohd-akram. Thank you for your contributions!