@sentry/remix
Advanced tools
Changelog
8.0.0-beta.1
This is the first beta release of Sentry JavaScript SDK v8. With this release, there are no more planned breaking changes for the v8 cycle.
Read the in-depth migration guide to find out how to address any breaking changes in your code. All
deprecations from the v7 cycle, with the exception of getCurrentHub()
, have been removed and can no longer be used in
v8.
The Sentry JavaScript SDK v8 now supports Node.js 14.8.0 or higher. This applies to @sentry/node
and all of our
node-based server-side sdks (@sentry/nextjs
, @sentry/remix
, etc.).
The browser SDKs now require ES2018+ compatible browsers. New minimum browser versions:
For more details, please see the version support section in migration guide.
The following packages will no longer be published
Changelog
Important Changes since v8.0.0-alpha.9
Because execution context isolation in browser environments does not work reliably, we deciced to keep a flat span hierarchy by default in v8.
addTracingExtensions
(#11579)Instead of calling Sentry.addTracingExtensions()
if you want to use performance in a browser SDK without using
browserTracingIntegration()
, you should now call Sentry.registerSpanErrorInstrumentation()
.
suppressTracing
(#11468)You can use the new suppressTracing
API to ensure a given callback will not generate any spans:
return Sentry.suppressTracing(() => {
// Ensure this fetch call does not generate a span
return fetch('/my-url');
});
import
and loader
(#11498)We renamed the loader hooks for better clarity:
Changelog
8.0.0-alpha.8
This is a partially broken release and was superseded by version 8.0.0-alpha.9
.
Changelog
8.0.0-alpha.7
This is the seventh alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.
Read the in-depth migration guide to find out how to address any breaking changes in your code.
We now use OpenTelemetry under the hood to power performance monitoring and tracing in the Next.js SDK.
In v8, you cannot initialize the SDK anymore via Gatsby plugin options. Instead, you have to configure the SDK in a
sentry.config.js
file.
We also removed the automatic initialization of browserTracingIntegration
. You now have to add this integration
yourself.
scope.setSpan()
and scope.getSpan()
methods (#11051)runtime
and vercel
tags (#11291)prismaIntegration
by default (#11265)tracePropagationTargets
are respected (#11285)SentrySpanProcessor
(#11273)instrumentation.ts
) (#11266)suppressTracing
to avoid capturing otel spans (#11288)startSpan
callback throws (#11170)Changelog
8.0.0-alpha.5
This is the fifth alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.
Read the in-depth migration guide to find out how to address any breaking changes in your code.
client.(server|client).config.ts
functionality in favor of instrumentation.ts
(#11059)
13.2.0
(#11097)With version 8 of the SDK we will no longer support the use of sentry.server.config.ts
and sentry.edge.config.ts
files. Instead, please initialize the Sentry Next.js SDK for the serverside in a
Next.js instrumentation hook.
sentry.client.config.ts|js
is still supported and encouraged for initializing the clientside SDK. Please see the
Migration Guide for more details.
In addition, the Next.js SDK now requires a minimum Next.js version of 13.2.0
.
The @sentry/angular-ivy
package has been removed. The @sentry/angular
package now supports Ivy by default and
requires at least Angular 14. See the Migration Guide for more
details.
rethrowAfterCapture
option (#11126)tunnel
option for ANR (#11163)@sentry/node
package (#11075)view_hierarchy
attachment type (#11197)initOpenTelemetry
(#11158)cron
(#11225)sampled
type on Transaction
(#11115)Changelog
8.0.0-alpha.4
This is the fourth Alpha release of the v8 cycle, which includes a variety of breaking changes.
Read the in-depth migration guide to find out how to address any breaking changes in your code.
The minimum Node version required for the SDK is now 14.18.0
.
@sentry/google-cloud-serverless
(#11065)@sentry/serverless
is no longer published, and is replaced by two new packages: @sentry/google-cloud-serverless
and
@sentry/aws-serverless
. These packages are now the recommended way to instrument serverless functions. See the
migration guide for more details.
The Browser SDK and CDN bundles now emits ES2017 compatible code and drops support for IE11. This also means that the
Browser SDKs (@sentry/browser
, @sentry/react
, @sentry/vue
, etc.) requires the fetch API to be available in the
environment. If you need to support older browsers, please transpile your code to ES5 using babel or similar and add
required polyfills.
New minimum supported browsers:
startTransaction
export (#11015)unmask
and unblock
(#11049)replaySession
and errorSampleRates
(#11045)spanRecorder
and all related code (#10977)origin
field on span start options (#11058)startSpan
options (#11054)startTransaction
& finishTransaction
hooks (#11008)sentry
field in Next.js config as a means of configuration (#10839)startChild
deprecations (#10956)getRootSpan()
does not rely on transaction (#10979)getSpanDescendants()
everywhere (#10924)transactionName
when route is resolved (#11043)name
parameter (#11057)@sentry/astro
to use OpenTelemetry (#10960)HttpContext
integration class (#10987)scope.transactionName
from root spans (#10991)startIdleSpan
(#10934)__SENTRY__
singleton (#11034)__SENTRY__
(#11074)continueTrace
to be callback-only (#11044)spanToJSON
to handle OTEL spans (#10922)tunnelRoute
option (#10959)setupFastifyErrorHandler
utility (#11061)getRootSpan
functionality (#11004)transactionName
in React Router instrumentations (#11048)unstable_sentryVitePluginOptions
for full Vite plugin customization (#10930)createReduxEnhancer
on server (#11005)handled
value in ErrorBoundary depending on fallback (#10989)addScopeListener
to Scope
interface (#10952)AttachmentType
and use for envelope attachment_type
property (#10946)allowSyntheticDefaultImports
(#11073)startChild
(#11056)scope.transactionName
on pageload and navigation span creation (#10992)startChild()
(#11047)http
& undici
(#11055)Work in this release contributed by @MFoster and @jessezhang91. Thank you for your contributions!