Releases: getsentry/sentry-javascript
7.13.0
- feat(browser): Use fetch
keepaliveflag (#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
normalizeDepthoption when creating an event from a plain object - fix(core): Fix integration deduping (#5696)
- fix(node): Use
normalizeDepthwhen 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):
contextscannot be overridden andculturenever 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
getInitialPropsandgetServerSideProps(#5593) - feat(nextjs): Instrument server-side
getInitialPropsof_app,_documentand_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.contextsfor 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
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
SentryErrorisn'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
jsonresponses from root loader functions. (#5548) - fix(remix): Return response if detected in root loader (#5558)
- ref(nextjs): Move
autoWrapDataFetchersoption intoexperimentsobject (#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
tracePropagationTargetsoption (#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
transpileClientSDKoption 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-traceandbaggagevia root loader. (#5509) - ref(nextjs): Prework for wrapping data-fetching functions (#5508)
- ref(nextjs): Simplify
NextConfigObjecttype (#5514)
7.8.1
- fix(nextjs): Add default
distDirvalue 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
captureUnderscoreErrorExceptionargument type (#5463) - fix(nextjs): Stop using
evalwhen checking forsentry-clibinary (#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
isBuildinto an exported function (#5444) - ref(nextjs): Remove compensation for workaround in
_error.js(#5378) - ref(nextjs): Use loader to set
RewriteFrameshelper 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!