Releases: getsentry/sentry-javascript
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 intoexperiments
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
andbaggage
via root loader. (#5509) - ref(nextjs): Prework for wrapping data-fetching functions (#5508)
- ref(nextjs): Simplify
NextConfigObject
type (#5514)
7.8.1
- fix(nextjs): Add default
distDir
value back intoindex.server.ts
(#5479) - fix(node): Add conditions to TracingHandler.startTransaction (#5485)
- fix(node): Adjust Express URL parameterization for array routes (#5495)
- fix(node): Adjust Express URL parameterization for RegEx routes (#5483)
- fix(node): Check if router exists before it is instrumented (#5502)
- fix(node): Correctly handle Windows paths when resolving module name (#5476)
- fix(node): Ensure that self._handler exists before calling it in LinkedErrors (#5497)
- ref(tracing): Simplify sample_rate serialization for DSC (#5475)
7.8.0
This release adds the transpileClientSDK
flag to the Next.JS SDK Webpack config. This option makes WebPack transpile the SDK code to the same transpilation level as the user code. By specifying this option, the Next.JS SDK works in older browsers that do not support ES6 or ES6+ (e.g. object spread) features.
- feat(react): Use state context for Redux integration (#5471)
- feat(remix): Set sentry-trace and baggage tags on server-side (#5440)
- feat(tracing): Allow storing span metadata (#5464)
- feat(tracing): Log start and end of span (#5446)
- fix(nextjs): Add transpileClientSDK option (#5472)
- fix(nextjs): Move userNextConfig.sentry to closure (#5473)
- fix(nextjs): Remove index signaure in
captureUnderscoreErrorException
argument type (#5463) - fix(nextjs): Stop using
eval
when checking forsentry-cli
binary (#5447) - fix(remix): Clone erroneous responses not to consume their body streams. (#5429)
- fix(remix): Do not capture 4xx codes from thrown responses. (#5441)
- ref(angular): Set ErrorHandler Exception Mechanism to be unhandled by default(#3844)
- ref(nextjs): Extract
isBuild
into an exported function (#5444) - ref(nextjs): Remove compensation for workaround in
_error.js
(#5378) - ref(nextjs): Use loader to set
RewriteFrames
helper value (#5445) - ref(node): Improve Express URL Parameterization (#5450)
- ref(utils): Improve uuid generation (#5426)
Work in this release contributed by @mitchheddles. Thank you for your contribution!
7.7.0
7.6.0
This release adds the source
field to all outgoing transactions.
See the tracking GH issue for more details.
This release also re-enables lambda layer releases for the Node Serverless SDK.
- ref(angular): Add transaction source for Angular Router (#5382)
- ref(build): Reenable lambda layer release in craft (#5207)
- feat(nextjs): Record transaction name source when creating transactions (#5391)
- ref(react): Add source to react-router-v3 (#5377)
- ref(react): Add transaction source for react router v4/v5 (#5384)
- ref(react): Add transaction source for react router v6 (#5385)
- feat(remix): Wrap root with ErrorBoundary (#5365)
- fix(remix): Move hook checks inside the wrapper component (#5371)
- fix(remix): Strip query params from transaction names (#5368)
- fix(remix): Make peer deps less restrictive (#5369)
- fix(remix): Wrap handleDocumentRequest functions (#5387)
- ref(serverless): Add transaction source (#5394)
- feat(tracing): Add transaction source field (#5367)
- feat(tracing): Record transaction name source when name set directly (#5396)
- ref(tracing): Add transaction source to default router (#5386)
- ref(tracing): Include transaction in DSC if transaction source is not an unparameterized URL (#5392)
- feat(vue): Add transaction source to VueRouter instrumentation (#5381)
Work in this release contributed by @moishinetzer. Thank you for your contribution!
7.5.1
7.5.0
This release adds the sendDefaultPii
flag to the Sentry.init
options.
When using performance monitoring capabilities of the SDK, it controls whether user IDs (set via Sentry.setUser
) are propagated in the baggage
header of outgoing HTTP requests.
This flag is set to false
per default, and acts as an opt-in mechanism for sending potentially sensitive data.
If you want to attach user IDs to Sentry transactions and traces, set this flag to true
but keep in mind that this is potentially sensitive information.
- feat(sdk): Add sendDefaultPii option to the JS SDKs (#5341)
- fix(remix): Sourcemaps upload script is missing in the tarball (#5356)
- fix(remix): Use cjs for main entry point (#5352)
- ref(tracing): Only add
user_id
to DSC ifsendDefaultPii
istrue
(#5344)
Work in this release contributed by @jkcorrea and @nfelger. Thank you for your contributions!