Official Sentry SDKs for JavaScript
MIT License
Bot releases are visible (Hide)
Published by getsentry-bot over 1 year ago
app
directory browser bundle (#6812)includeLocalVariables
option to enable LocalVariables
integration (#6874)flush
method to integration (#6776)enableLongTask
to option of BrowserTracing
(#6837)initialFlushDelay
option (#6867)Work in this release contributed by @h3rmanj. Thank you for your contribution!
Published by getsentry-bot almost 2 years ago
Published by getsentry-bot almost 2 years ago
The Next.js SDK now supports error and performance monitoring for Next.js middleware and Edge API routes.
To set it up, add a sentry.edge.config.js
or sentry.edge.config.ts
file to the root of your project and initialize the SDK:
// sentry.edge.config.js or sentry.edge.config.ts
import * as Sentry from "@sentry/nextjs";
const SENTRY_DSN = process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN;
Sentry.init({
dsn: SENTRY_DSN || "YOUR DSN HERE",
tracesSampleRate: 1.0,
});
The Next.js will automatically instrument Edge API routes and middleware.
If you want to opt out of automatic instrumentation of middleware can use the autoInstrumentMiddleware
option in the sentry
object of your Next.js configuration:
const moduleExports = {
sentry: {
autoInstrumentMiddleware: false,
},
};
Middleware can be manually instrumented by using the wrapMiddlewareWithSentry
function.
withSentryConfig
as an alternative to the sentry
property (#6721)checkoutEveryNms
(#6722)isBuild()
and IS_BUILD
(#6727)Published by getsentry-bot almost 2 years ago
addIntegration
method to client (#6651)replay_event
type for events (#6481)LocalVariables
integration to capture local variables to stack frames (#6478)replayType
from tags and into replay_event
(#6658)res.json
and res.send
(#6674)res.end
to fix next export
(#6682)instrumentSever
(#6592)Work in this release contributed by @rjoonas, @Naddiseo, and @theofidry. Thank you for your contributions!
Published by getsentry-bot almost 2 years ago
This update includes a change to the @sentry/nextjs
SDK that may increase response times of requests in applications
deployed to Vercel or AWS lambdas to ensure that error events are sent consistently.
Additionally, Next.js applications deployed to Vercel or AWS lambdas may also see an uptick in sent transactions. (for
more information see #6578)
getSdkMetadata
to Client
(#6643)prepareEvent
util & ensure dropping replays works (#6522)maskAllText
selector (#6637)pageload
transactions early (#6609)Published by getsentry-bot almost 2 years ago
_metadata
in client options (#6600)Published by getsentry-bot almost 2 years ago
index.server.ts
to avoid TS error (#6577)this
through wrappers (#6572)undefined
as possible event type (#6584)Published by getsentry-bot almost 2 years ago
This release exports the Session Replay integration via @sentry/browser
and all framework SDKs building on top of it.
Going forward, the @sentry/replay
package doesn't have to be installed explicitly to use Replay.
Furthermore, this release increases the maximim replay session duration from 30 minutes to 1 hour.
Replay
integration from Browser SDK (#6508)MAX_SESSION_LIFE
to 1 hour (#6561)beforeSend
handling defensive for different event types (#6507)maskAllText
selector more specific (#6544)dsn
in envelope header if tunneling is active (#6568)Work in this release contributed by @theofidry. Thank you for your contribution!
Published by getsentry-bot almost 2 years ago
Work in this release contributed by @theofidry. Thank you for your contribution!
Published by getsentry-bot almost 2 years ago
scope.getLastBreadcrumb()
(#6495)_waitForError
with recordingMode
(#6489)Published by getsentry-bot almost 2 years ago
reportAllChanges
option (#6456)Published by getsentry-bot almost 2 years ago
This patch corrects an oversight on our end which caused the Sentry Replay integration CDN bundles to be ignored when uploading bundles to our CDN.
If you want to use the Replay CDN bundles, please use version 7.24.1 or newer.
encodeLocation
method (#6439)Work in this release contributed by @theofidry. Thank you for your contribution!
Published by getsentry-bot almost 2 years ago
This release bumps the @sentry/replay
package from version 0.x to 7.24.0.
Along with this version bump, we're introducing a few breaking changes.
Take a look at the Replay migration guide for further information.
Furthermore, we're now also publishing CDN bundles for the Replay integration.
The Replay version bump is the result of moving the package into the Sentry JavaScript SDK monorepo which aligns the version with our other JS SDK packages.
assetPrefix
option (#6388)basePath
for assetPrefix
if needed (#6424)profilesSampleRate
into BaseNodeOptions
(#6409)getClientIpAddress
throws error. (#6400)Work in this release contributed by @tomgrossman and @ZachGawlik. Thank you for your contributions!
Published by getsentry-bot almost 2 years ago
__SENTRY_RELEASE__
magic string (#6322)profilesSampleRate
(#6318)sentry_reportAllChanges
tag (#6360)Work in this release contributed by @zhiyan114. Thank you for your contributions!
Published by getsentry-bot almost 2 years ago
event
as third argument to recordDroppedEvent
(#6289)RouteObject
typing. (#6274)normalizeRemixRequest
calls. (#6296)RequestData
. (#6276)Published by getsentry-bot almost 2 years ago
withSentryConfig
from serverless bundles (#6267)Published by getsentry-bot almost 2 years ago
createBrowserRouter
. (#6172)tracePropagationTargets
to instrumentOutgoingRequests
(#6259)Published by getsentry-bot almost 2 years ago
<unknown>
component name default in TraceDirective (#6222)_sdkProcessingMetadata
when cloning scope (#6218)shouldAttachHeaders
not fall back to default values (#6238)Published by getsentry-bot almost 2 years ago
excludeServerRoutes
config option (#6207)Http
integration (#6191)distDir
in webpack plugin options (#6214)Published by getsentry-bot almost 2 years ago
This release adds a new SDK, @sentry/opentelemetry-node,
which is available as an alpha release to integrate OpenTelemetry performance tracing with Sentry.
Give it a try and let us know if you have any feedback or problems with using it. (#6000)
This release also deprecates the tracingOrigins
option in favor of using shouldCreateSpanForRequest
and tracePropagationTargets
.
See #6176 for details.
transaction.setContext
method (#6154)instrumenter
on Span & Transaction (#6136)tracingOrigins
(#6176)