Official Sentry SDK for Vercel Edge Runtime [ALPHA]
Links
Note: This SDK is still in an alpha state. Breaking changes can occur at any time.
Usage
To use this SDK, call init(options)
as early as possible in the main entry module. This will initialize the SDK and
hook into the environment. Note that you can turn off almost all side effects using the respective options.
const Sentry = require('@sentry/vercel-edge');
import * as Sentry from '@sentry/vercel-edge';
Sentry.init({
dsn: '__DSN__',
});
To set context information or send manual events, use the exported functions of @sentry/vercel-edge
. Note that these
functions will not perform any action before you have called init()
:
Sentry.setExtra('battery', 0.7);
Sentry.setTag('user_mode', 'admin');
Sentry.setUser({ id: '4711' });
Sentry.addBreadcrumb({
message: 'My Breadcrumb',
});
Sentry.captureMessage('Hello, world!');
Sentry.captureException(new Error('Good bye'));
Sentry.captureEvent({
message: 'Manual',
stacktrace: [
],
});
8.20.0
Important Changes
- feat(node): Allow to pass
registerEsmLoaderHooks
to preload (#12998)
You can write your own custom preload script and configure this in the preload options. registerEsmLoaderHooks
can be
passed as an option to preloadOpenTelemetry
, which allows to exclude/include packages in the preload.
- fix(node): Do not emit fetch spans when tracing is disabled (#13003)
Sentry will not emit "fetch" spans if tracing is disabled. This is relevant for user who use their own sampler.
Other Changes
- feat(feedback): Trigger button aria label configuration (#13008)
- feat(nestjs): Change nest sdk setup (#12920)
- feat(node): Extend ESM hooks options for iitm v1.10.0 (#13016)
- feat(node): Send client reports (#12951)
- feat(nuxt): Automatically add BrowserTracing (#13005)
- feat(nuxt): Setup source maps with vite config (#13018)
- feat(replay): Improve public Replay APIs (#13000)