@sentry/vercel-edge
Advanced tools
Changelog
8.10.0
opentelemetry-instrumentation-remix
. (#12110)You can now simplify your remix instrumentation by opting-in like this:
const Sentry = require('@sentry/remix');
Sentry.init({
dsn: YOUR_DSN
// opt-in to new auto instrumentation
autoInstrumentRemix: true,
});
With this setup, you do not need to add e.g. wrapExpressCreateRequestHandler
anymore. Additionally, the quality of the
captured data improves. The old way to use @sentry/remix
continues to work, but it is encouraged to use the new setup.
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!
Changelog
8.9.2
Changelog
8.9.1
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 the
package README for how to use
the SDK.
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!
Changelog
8.8.0
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 like discord.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)Work in this release contributed by @dohooo, @mohd-akram, and @ykzts. Thank you for your contributions!
Changelog
8.7.0
feat(react): Add TanStack Router integration (#12095)
This release adds instrumentation for TanStack router with a new tanstackRouterBrowserTracingIntegration
in the
@sentry/react
SDK:
import * as Sentry from '@sentry/react';
import { createRouter } from '@tanstack/react-router';
const router = createRouter({
// Your router options...
});
Sentry.init({
dsn: '___PUBLIC_DSN___',
integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)],
tracesSampleRate: 1.0,
});
sourceMappingURL
comment on client when nextConfig.productionBrowserSourceMaps: true
is
set (#12278)Changelog
8.6.0
feat(metrics): Add timings
method to metrics (#12226)
This introduces a new method, metrics.timing()
, which can be used in two ways:
second
as unit:Sentry.metrics.timing('myMetric', 100);
const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction);
feat(react): Add Sentry.reactErrorHandler
(#12147)
This PR introduces Sentry.reactErrorHandler
, which you can use in React 19 as follows:
import * as Sentry from '@sentry/react';
import { hydrateRoot } from 'react-dom/client';
ReactDOM.hydrateRoot(
document.getElementById('root'),
<React.StrictMode>
<App />
</React.StrictMode>,
{
onUncaughtError: Sentry.reactErrorHandler(),
onCaughtError: Sentry.reactErrorHandler((error, errorInfo) => {
// optional callback if users want custom config.
}),
},
);
For more details, take a look at the PR. Our documentation will be updated soon!
Changelog
8.5.0
This release adds support for React 19 in the @sentry/react
SDK package.
@sentry/node/preload
hook (#12213)This release adds a new way to initialize @sentry/node
, which allows you to use the SDK with performance
instrumentation even if you cannot call Sentry.init()
at the very start of your app.
First, run the SDK like this:
node --require @sentry/node/preload ./app.js
Now, you can initialize and import the rest of the SDK later or asynchronously:
const express = require('express');
const Sentry = require('@sentry/node');
const dsn = await getSentryDsn();
Sentry.init({ dsn });
For more details, head over to the PR Description of the new feature. Our docs will be updated soon with a new guide.
startNewTrace
API (#12138)captureFeedback()
(#12216)SerializedSession
in session envelope items (#11979)waitUntil
to defer freezing of Vercel Lambdas (#12133)Module._resolveFilename
in Lambda layer bundle (#12232)ImportInTheMiddle
(#12233)@prisma/instrumentation
to use default import (#12185)inspector
asynchronously (#12231)Changelog
8.4.0
If you are using Next.js version 14.3.0-canary.64
or above, the Sentry Next.js SDK will now trace clientside pageloads
with React Server Components. This means, that client-side errors like
Error: An error occurred in the Server Components render.
, which previously didn't give you much information on how
that error was caused, can now be traced back to a specific error in a server component.
This release guarantees support for Angular 18 with @sentry/angular
.