Update sentry-javascript monorepo to v8 (master) (major) - autoclosed #9433
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.118.0
->8.26.0
7.118.0
->8.26.0
Release Notes
getsentry/sentry-javascript (@sentry/browser)
v8.26.0
Compare Source
Important Changes
feat(node): Add
fsInstrumentation
(#13291)This release adds
fsIntegration
, an integration that instruments thefs
API to the Sentry Node SDK. Theintegration creates spans with naming patterns of
fs.readFile
,fs.unlink
, and so on.This integration is not enabled by default and needs to be registered in your
Sentry.init
call. You can configurevia options whether to include path arguments or error messages as span attributes when an fs call fails:
WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of
file I/O, like for example when running a framework dev server, including this integration can massively slow down
your application.
Other Changes
feat(browser): Add spotlightBrowser integration (#13263)
feat(browser): Allow sentry in safari extension background page (#13209)
feat(browser): Send CLS as standalone span (experimental) (#13056)
feat(core): Add OpenTelemetry-specific
getTraceData
implementation (#13281)feat(nextjs): Always add
browserTracingIntegration
(#13324)feat(nextjs): Always transmit trace data to the client (#13337)
feat(nextjs): export SentryBuildOptions (#13296)
feat(nextjs): Update
experimental_captureRequestError
to reflectRequestInfo.path
change in Next.js canary(#13344)
feat(nuxt): Always add tracing meta tags (#13273)
feat(nuxt): Set transaction name for server error (#13292)
feat(replay): Add a replay-specific logger (#13256)
feat(sveltekit): Add bundle size optimizations to plugin options (#13318)
feat(sveltekit): Always add browserTracingIntegration (#13322)
feat(tracing): Make long animation frames opt-out (#13255)
fix(astro): Correctly extract request data (#13315)
fix(astro): Only track access request headers in dynamic page requests (#13306)
fix(nuxt): Add import line for disabled
autoImport
(#13342)fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)
fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)
fix(remix): Ensure
origin
is correctly set for remix server spans (#13305)Work in this release was contributed by @MonstraG, @undead-voron and @Zen-cronic. Thank you for your contributions!
v8.25.0
Compare Source
Important Changes
This release contains the alpha version of
@sentry/solidstart
, our SDK for Solid Start!For details on how to use it, please see the README. Any feedback/bug reports are
greatly appreciated, please reach out on GitHub.
Other Changes
bundleSizeOptimizations
vite options to integration (#13250)getTraceMetaTags
function (#13201)useOperationNameForRootSpan
tographqlIntegration
(#13248)wrapServerRouteWithSentry
wrapper (#13247)context
overevent
(#13266)defaultIntegrations: undefined
(#13261)v8.24.0
Compare Source
v8.23.0
Compare Source
Important Changes
This release includes support for Cloudflare D1, Cloudflare's serverless SQL database. To instrument your Cloudflare D1
database, use the
instrumentD1WithSentry
method as follows:Other Changes
getTraceData
function (#13134)onBeforeResponse
middleware to enable distributed tracing (#13221)window
global scopes (#13156)\_loadAndRenderDialog
(#13203)Work in this release was contributed by @horochx. Thank you for your contribution!
v8.22.0
Compare Source
Important Changes
This release adds support for Cloudflare Pages to
@sentry/cloudflare
, our SDK for theCloudflare Workers JavaScript Runtime! For details on how to use it,
please see the README. Any feedback/bug reports are greatly appreciated, please
reach out on GitHub.
Other Changes
internal_sdk_error
client report happens (#13072)globalThis
for code injection (#13132)v8.21.0
Compare Source
Important Changes
withSentry
method (#13025)This release contains the alpha version of
@sentry/cloudflare
, our SDK for theCloudflare Workers JavaScript Runtime! For details on how to use it,
please see the README. Any feedback/bug reports are greatly appreciated, please
reach out on GitHub.
Please note that only Cloudflare Workers are tested and supported - official Cloudflare Pages support will come in an
upcoming release.
Other Changes
beforeSendTransaction
(#13022)v8.20.0
Compare Source
Important Changes
registerEsmLoaderHooks
to preload (#12998)You can write your own custom preload script and configure this in the preload options.
registerEsmLoaderHooks
can bepassed as an option to
preloadOpenTelemetry
, which allows to exclude/include packages in the preload.Sentry will not emit "fetch" spans if tracing is disabled. This is relevant for user who use their own sampler.
Other Changes
v8.19.0
Compare Source
node --import=@sentry/node/import app.js
v8.18.0
Compare Source
Important Changes
enableTracing
(12897)The
enableTracing
option has been deprecated and will be removed in the next major version. We recommend removing itin favor of the
tracesSampleRate
andtracesSampler
options. If you want to enable performance monitoring, please setthe
tracesSampleRate
to a sample rate of your choice, or provide a sampling function astracesSampler
optioninstead. If you want to disable performance monitoring, remove the
tracesSampler
andtracesSampleRate
options.Other Changes
exclude
andinclude
options for ESM loader (#12910)experimental_captureRequestError
foronRequestError
hook (#12885)rrweb
to 2.25.0 (#12478)ErrorEvent
check in ErrorHandler to avoid throwing in Node environments (#12892)ignoreIncomingRequests
callback (#12929)otel.kind: INTERNAL
attribute (#12841)null
asparentSpan
instartSpan*
(#12928)Work in this release was contributed by @GitSquared and @mcous. Thank you for your contributions!
Bundle size 📦
v8.17.0
Compare Source
v8.16.0
Compare Source
Important Changes
Previously, the
@sentry/nextjs
SDK automatically recorded spans in the form of transactions for each of your top-levelserver components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have
a root span, and more importantly, if you had data stream to the client, its duration was not captured because the
server component spans had finished before the data could finish streaming.
With this release, we will capture the duration of App Router requests in their entirety as a single transaction with
server component spans being descendants of that transaction. This means you will get more data that is also more
accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it
has before.
Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no
longer receive server component transactions like
Page Server Component (/path/to/route)
(unless using the Edgeruntime), and you will instead receive transactions for your App Router SSR requests that look like
GET /path/to/route
.If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.
The
@sentry/nestjs
SDK now includes a@SentryCron
decorator that can be used to augment the native NestJS@Cron
decorator to send check-ins to Sentry before and after each cron job run:
Other Changes
httpIntegration
(#12761)addPluginTemplate
(#12760)h
import inScreenshotEditor
(#12784)autoSessionTracking
is enabled by default (#12790)v8.15.0
Compare Source
on
(#11710)spanTimeInputToSeconds
for otel span exporter (#12699)lazyLoadIntegration
(#12766)jsxRuntime: 'classic'
to prevent breaking react 17 (#12775)getStack()
(#12737)Work in this release was contributed by @arturovt and @jaulz. Thank you for your contributions!
v8.14.0
Compare Source
Important Changes
The
@sentry/nestjs
SDK no longer captures 4xx errors automatically.Other Changes
JSX
(#12691)registerEsmLoaderHooks
option (#12684)afterAllSetup
instead of next tick (#12709)Work in this release was contributed by @quisido. Thank you for your contribution!
v8.13.0
Compare Source
Important Changes
@sentry/nestjs
)in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (
@sentry/node
) supporting the same set offeatures. See the docs for how to use the SDK.
Other Changes
2.20.1
(#12641)v8.12.0
Compare Source
Important Changes
This release introduces breaking changes to the
@sentry/solid
package (which is currently out in alpha).We've made it easier to get started with the solid router integration by removing the need to pass use* hooks
explicitly to
solidRouterBrowserTracingIntegration
. ImportsolidRouterBrowserTracingIntegration
from@sentry/solid/solidrouter
and add it toSentry.init
Sentry.init()
now returns a client directly, so you don't need to explicitly callgetClient()
anymore:deleteSourcemapsAfterUpload
option (#12457)This adds an easy way to delete sourcemaps immediately after uploading them:
maxSpanWaitDuration
(#12610)Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before
discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is
necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However,
if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early.
In this case, you can increase this duration to a value that fits your expected data.
Other Changes
window.Sentry
(#12580)isRemixV2
as optional in exposed types. (#12614)Work in this release was contributed by @n4bb12. Thank you for your contribution!
v8.11.0
Compare Source
Important Changes
parentSpan
option tostartSpan*
APIs (#12567)We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to
explicitly manage the parent-child relationship of your spans better.
Other Changes
@sentry/node
exports from framework SDKs. (#12589)Bundle size 📦
v8.10.0
Compare Source
Important Changes
opentelemetry-instrumentation-remix
. (#12110)You can now simplify your remix instrumentation by opting-in like this:
With this setup, you do not need to add e.g.
wrapExpressCreateRequestHandler
anymore. Additionally, the quality of thecaptured data improves. The old way to use
@sentry/remix
continues to work, but it is encouraged to use the new setup.Other Changes
thirdPartyErrorFilterIntegration
from@sentry/browser
(#12512)tags
field to any feedback config param (#12197)getDynamicSamplingContextFromSpan
(#12522)captureRemixServerException
from client SDK (#12497)Work in this release was contributed by @AndreyKovanov and @kiliman. Thank you for your contributions!
v8.9.2
Compare Source
v8.9.1
Important changes
feat(solid): Add Solid SDK
This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for
Solid Router and a custom
ErrorBoundary
. See thepackage README for how to use
the SDK.
Other changes
op
to Otel-generated lambda function root span (#12430)awslambda-auto
(#12392)Work in this release was contributed by @soch4n. Thank you for your contribution!
v8.9.0
This release failed to publish correctly, please use
8.9.1
instead.v8.8.0
Compare Source
This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use
import-in-the-middle
v1.8.0
.This should fix numerous issues with using OTEL instrumentation with ESM.
High level issues fixed with OTEL + ESM:
tsx
or similar libraries.date-fns
.openai
.ENOENT: no such file or directory
bugs that libraries likediscord.js
surface.
If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know.
2.18.0
(#12381)thirdPartyErrorFilterIntegration
(#12267)mget
command in caching functionality (#12380)clientTraceMetadata
option (#12323)sentry
property on Next.js config object (#12366)Configuration
📅 Schedule: Branch creation - "after 5pm on the first day of the month" in timezone Europe/Zurich, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.