@sentry/core - npm Package Versions

8.2.1

• fix(aws-serverless): Fix build of lambda layer (#12083)
• fix(nestjs): Broaden nest.js type (#12076)

8.2.0

• feat(redis-cache): Create cache-span with prefixed keys (get/set commands) (#12070)
• feat(core): Add beforeSendSpan hook (#11886)
• feat(browser): Improve idle span handling (#12065)
• fix(node): Set transactionName for unsampled spans in httpIntegration (#12071)
• fix(core): Export Scope interface as Scope (#12067)
• fix(core): Avoid looking up client for hasTracingEnabled() if possible (#12066)
• fix(browser): Use consistent timestamps (#12063)
• fix(node): Fix check for performance integrations (#12043)
• ref(sveltekit): Warn to delete source maps if Sentry plugin enabled source maps generation (#12072)

8.1.0

This release mainly fixes a couple of bugs from the initial 8.0.0 release. In addition to the changes below, we updated some initially missed points in our migration guides and documentation.

• feat(aws-serverless): Fix tree-shaking for aws-serverless package (#12017)
• feat(node): Bump opentelemetry instrumentation to latest version (#12028)
• feat(scope): Bring back lastEventId on isolation scope (#11951) (#12022)
• fix(aws-serverless): Export awslambda-auto
• fix(node): Do not warn for missing instrumentation if SDK is disabled (#12041)
• fix(react): Set dependency-injected functions as early as possible (#12019)
• fix(react): Warn and fall back gracefully if dependency injected functions are not available (#12026)
• ref(core): Streamline parseSampleRate utility function (#12024)
• ref(feedback): Make eventId optional and use lastEventId in report dialog (#12029)

8.0.0

The Sentry JS SDK team is proud to announce the release of version 8.0.0 of Sentry's JavaScript SDKs - it's been a long time coming! Thanks to everyone for your patience and a special shout out to the brave souls testing preview builds and reporting issues - we appreciate your support!

How to Upgrade to Version 8:

We recommend reading the migration guide docs to find out how to address any breaking changes in your code for your specific platform or framework.

To automate upgrading to v8 as much as possible, use our migration codemod @sentry/migr8:

npx @sentry/migr8@latest

All deprecations from the v7 cycle, with the exception of getCurrentHub(), have been removed and can no longer be used in v8. If you have an advanced Sentry SDK setup, we additionally recommend reading the in-depth migration guide in our repo which highlights all changes with additional details and information.

The rest of this changelog highlights the most important (breaking) changes and links to more detailed information.

Version Support

With v8, we dropped support for several old runtimes and browsers

Node SDKs: 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.). Furthermore, version 8 now ships with full support for ESM-based node apps using Node.js 18.19.0 or higher.

Browser SDKs: The browser SDKs now require ES2018+ compatible browsers. New minimum browser versions:

• Chrome 63
• Edge 79
• Safari/iOS Safari 12
• Firefox 58
• Opera 50
• Samsung Internet 8.2

For more details, please see the version support section in our migration guide.

Initializing Server-side SDKs (Node, Bun, Deno, Serverless):

In v8, we support a lot more node-based packages than before. In order to ensure auto-instrumentation works, the SDK now needs to be imported and initialized before any other import in your code.

We recommend creating a new file (e.g. instrumentation.js) to import and initialize the SDK. Then, import the file on top of your entry file or detailed instructions, check our updated SDK setup docs initializing the SDK in v8.

Performance Monitoring Changes

The API around performance monitoring and tracing has been streamlined, and we've added support for more integrations out of the box.

• Performance Monitoring API
• Performance Monitoring Integrations

Functional Integrations

Integrations are now simple functions instead of classes. Class-based integrations have been removed:

// old (v7)
Sentry.init({
  integrations: [new Sentry.BrowserTracing()],
});

// new (v8)
Sentry.init({
  integrations: [Sentry.browserTracingIntegration()],
});

Package removal

The following packages have been removed or replaced and will no longer be published:

• @sentry/hub
• @sentry/tracing
• @sentry/integrations
• @sentry/serverless
• @sentry/replay

Changes since 8.0.0-rc.3

• feat(nextjs): Remove transpileClientSDK (#11978)

  As we are dropping support for Internet Explorer 11 and other other older browser versions wih version 8.0.0, we are also removing the transpileClientSDK option from the Next.js SDK. If you need to support these browser versions, please configure Webpack and Next.js to down-compile the SDK.

• feat(serverless): Do not include performance integrations by default (#11998)

  To keep Lambda bundle size reasonable, the SDK no longer ships with all performance (database) integrations by default. Add the Sentry integrations of the databases and other tools you're using manually to your Sentry.init call by following this guide. Note that this change does not apply if you use the SDK with the Sentry AWS Lambda layer.

• feat(feedback): Simplify public css configuration for feedback (#11985)

• fix(feedback): Check for empty user (#11993)

• fix(replay): Fix type for replayCanvasIntegration (#11995)

• fix(replay): Fix user activity not being updated in start() (#12001)

8.0.0-rc.2

Important Changes

• feat(node): Register ESM patching hooks in init for supported Node.js versions

This release includes adds support for ESM when Sentry.init() is called within a module imported via the --import Node.js flag:

node --import ./your-file-with-sentry-init.mjs your-app.mjs

Note that the SDK only supports ESM for node versions 18.19.0 and above, and 20.6.0 above.

Other Changes

• deps(node): Bump @opentelemetry/core to 1.24.1 and @opentelemetry/instrumentation to 0.51.1 (#11941)
• feat(connect): Warn if connect is not instrumented (#11936)
• feat(express): Warn if express is not instrumented (#11930)
• feat(fastify): Warn if fastify is not instrumented (#11917)
• feat(hapi): Warn if hapi is not instrumented (#11937)
• feat(koa): Warn if koa is not instrumented (#11931)
• fix(browser): Continuously record CLS web vital (#11934)
• fix(feedback): Pick user from any scope (#11928)
• fix(node): Fix cron instrumentation and add tests (#11811)

8.0.0-rc.1

This release contains no changes and was done for technical purposes. This version is considered stable.

For the sake of completeness this changelog entry includes the changes from the previous release candidate:

We recommend to read the detailed migration guide in the docs.

Important Changes

• feat(node): Support hapi v21 & fix E2E test (#11906)

We now support hapi v21 and added tests for it.

• feat(node): Warn if ESM mode is detected (#11914)

When running Sentry in ESM mode, we will now warn you that this is not supported as of now. We are working on ensuring support with ESM builds.

Other Changes

• feat(feedback): Iterate on css for better scrolling & resizing when browser is small (#11893)
• fix(node): Ensure prisma integration creates valid DB spans (#11908)
• fix(node): Include loader hook files in package.json (#11911)

8.0.0-rc.0

This is the first release candidate of Sentry JavaScript SDK v8.

We recommend to read the detailed migration guide in the docs.

Important Changes

• feat(node): Support hapi v21 & fix E2E test (#11906)

We now support hapi v21 and added tests for it.

• feat(node): Warn if ESM mode is detected (#11914)

When running Sentry in ESM mode, we will now warn you that this is not supported as of now. We are working on ensuring support with ESM builds.

Other Changes

• feat(feedback): Iterate on css for better scrolling & resizing when browser is small (#11893)
• fix(node): Ensure prisma integration creates valid DB spans (#11908)
• fix(node): Include loader hook files in package.json (#11911)