7.14.2

• fix(ember): Align span operations to new operations (#5883)
• fix(nextjs): Consider pageExtensions option in auto instrumentation (#5881)
• fix(remix): Align span operations to new operations (#5889)
• fix(serverless): Align span operations to new operations (#5890)
• fix(tracing): Align span operations to new operations (#5891)
• fix(vue): Align span operations to new operations (#5892)
• ref(hub): Remove hard cap from maxBreadcrumbs (#5873)
• ref(nextjs): Make build-phase check more robust (#5857)

Work in this release contributed by @outsideris. Thank you for your contributions!

7.14.1

• fix(nextjs): Handle CJS API route exports (#5865)
• fix(node): Only set DeviceContext.boot_time if os.uptime() is valid (#5859)
• fix(tracing): Warn if resolvers is not defined in ApolloServer config (#5850)
• fix(utils): Normalize when serializing envelope (#5851)
• ref(react): Improve React Router v6 error message (#5853)

7.14.0

• feat(nextjs): Add status to data-fetcher spans (#5777)
• feat(nextjs): Auto-wrap API routes (#5778)
• feat(nextjs): Promote option to automatically wrap data fetchers and API routes to non-experimental (#5793)
• feat(utils): Modern implementation of getGlobalObject (#5809)
• fix(gatsby): Include app-* entrypoints as they may include user source code (#5685)
• fix(nextjs): Handle pathname being passed in object in instrumentServer (#5782)
• fix(nextjs): Pass request in sampling context of data fetchers wrapper transaction (#5784)
• fix(nextjs): Reverse order of checks for instrumenting server (#5828)
• fix(nextjs): Rename nextjs.data.server ops (#5830)
• fix(remix): Do not skip error handling if tracing is not enabled. (#5811)
• fix(remix): Use import() to get react-router-dom in Express wrapper. (#5810)
• fix(tracing): Remove connection.downlink measurement (#5794)
• ref(browser): Use configured transport as fallback for client reports (#5797)
• ref(nextjs): Use flush code from withSentry in all backend wrappers (#5814)
• ref(nextjs): Use integration to add request data to transaction events (#5703)
• ref(nextjs): UseRequestData integration for errors (#5729)
• ref(node): Move request data functions back to @sentry/node (#5759)
• ref(tracing): Don't track transaction sampling method (#5775)
• ref(types): Use intersections instead of extend in envelope types (#5788)

Work in this release contributed by @Auspicus and @dagroe. Thank you for your contributions!

7.13.0

• feat(browser): Use fetch keepalive flag (#5697)
• feat(core): Set custom transaction source for event processors (#5722)
• feat(nextjs): Trace navigation transactions (#5676)
• feat(node): Add Modules integration to default integrations (#5706)
• fix(browser): Use normalizeDepth option when creating an event from a plain object
• fix(core): Fix integration deduping (#5696)
• fix(node): Use normalizeDepth when creating an event from unknown input
• fix(nextjs): Make NextApiHandler type version-agnostic (#5737)
• fix(tracing): Set sample rate in transaction metadata and DSC (#5691)
• ref: Make dynamic sampling context mutable (#5710)
• ref(tracing): Record transaction name changes (#5723)
• chore(nextjs): Remove obsolete dataFetchers loader (#5713)

7.12.1

• feat(nextjs): Connect trace between data-fetching methods and pageload (#5655)
• feat(react): Support useRoutes hook of React Router 6 (#5624)
• feat(remix): Continue transaction from request headers (#5600)
• feat(utils): Add function for ensuring input is an array (#5668)
• fix(utils): Remove Element dom type (#5675)
• fix(node): contexts cannot be overridden and culture never included (#5677)
• chore: Remove typedoc from READMEs (#5678)

7.12.0

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.

• fix(browser): use valid urls in Request checks (#5630)
• fix(integrations): Don't add empty stack trace in RewriteFrames (#5625)
• feat(nextjs): Create transactions in getInitialProps and getServerSideProps (#5593)
• feat(nextjs): Instrument server-side getInitialProps of _app, _document and _error (#5604)
• fix(nextjs): Start navigation transactions on same-route navigations (#5642)
• fix(nextjs): Don't run webpack plugin on non-prod Vercel deployments (#5603)
• ref(nextjs): Add warning about non-hidden sourcemaps (#5649)
• ref(nextjs): Use proxy loader for wrapping all data-fetching functions (#5602)
• feat(node): Populate event.contexts for Node.js (#5512)
• fix(node): Avoid catching domain errors in request handler (#5627)
• fix(serverless): Check for existence of callback in GCP event handler before calling (#5608)
• ref(tracing): Remove mark measurements (#5605)
• ref(tracing): Update long task description (#5601)
• chore(svelte): Detect and report SvelteKit usage (#5594)
• feat(svelte): Add Component Tracking (#5612)

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

7.11.1

• fix(remix): Store transaction on express req (#5595)

7.11.0

This release introduces updates the tracingOrigins option to not attach any headers/create an spans when supplied with an empty array ([]). Previously, we would supply the default tracingOrigins if an empty array was set as the tracingOrigins option.

• fix(core): Suppress stack when SentryError isn't an error (#5562)
• feat(nextjs): Wrap server-side getInitialProps (#5546)
• feat(nextjs): Improve pageload transaction creation (#5574)
• feat(nextjs): Add spans and route parameterization in data fetching wrappers (#5564)
• feat(nextjs): Create spans and route parameterization in server-side getInitialProps (#5587)
• fix(remix): Use domains to prevent scope bleed (#5570)
• fix(remix): Wrap domains properly on instrumentServer (#5590)
• feat(remix): Add route ID to remix routes (#5568)
• feat(remix): Export a manual wrapper for custom Express servers (#5524)
• feat(tracing): Add long task collection (#5529)
• feat(tracing): Allow for setting of an empty array (#5583)

7.10.0

This release introduces the first alpha version of @sentry/svelte, our newest JavaScript SDK! For details on how to use it, please see the README and the tracking GitHub issue.

• feat(react): Track duration of React component updates (#5531)
• feat(svelte): Add Error and Performance Instrumentation from Browser SDK (#5543)
• feat(svelte): Add Svelte SDK Package Boilerplate (#5535)
• fix(integration): Don't mangle localforage internals (#5534)
• fix(react): Set redux state context properly (#5550)
• fix(remix): Support merging json responses from root loader functions. (#5548)
• fix(remix): Return response if detected in root loader (#5558)
• ref(nextjs): Move autoWrapDataFetchers option into experiments object (#5540)
• ref(nextjs): Wrap server-side data-fetching methods during build (#5503)

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

7.9.0

This release adds the tracePropagationTargets option to the Sentry Node SDK.

• feat(node): Add tracePropagationTargets option (#5521)
• fix(browser): Parse Chrome stack frames without full paths (#5519)
• fix(browser): Set : as a part of gecko protocol regex group. (#4153)
• fix(browser): Strip webpack wrapping from stack frames (#5522)
• fix(nextjs): Pull transpileClientSDK option from correct location (#5516)
• fix(node): Handle colons in stack trace paths (#5517)
• fix(react): Fix React Router v6 paramaterization (#5515)
• fix(remix): Paramaterize server side transactions (#5491)
• fix(remix): Provide sentry-trace and baggage via root loader. (#5509)
• ref(nextjs): Prework for wrapping data-fetching functions (#5508)
• ref(nextjs): Simplify NextConfigObject type (#5514)