releases.shpreview
SentrySentry/Sentry Changelog

Internal JS SDK packages move to @sentry scope

June 15, 2026Sentry ChangelogView original ↗
16 enhancementsThis release16 enhancementsImprovements to existing featuresAI-tallied from the release notes

Starting from 10.58.0 release, our published internal packages used by the JavaScript SDK ecosystem have moved from the @sentry-internal/* scope to the @sentry/* scope.

For most Sentry users, no action is needed. If you install public SDK packages like @sentry/browser, @sentry/node, @sentry/react, or @sentry/nextjs, your package manager will resolve the updated dependencies as part of the normal SDK upgrade.

This change only matters if you directly depend on Sentry's internal packages, reference them in CI or release scripts, or pin them in custom tooling.

What changed

The following packages were renamed:

  • @sentry-internal/browser-utils -> @sentry/browser-utils starting from v10.58.0
  • @sentry-internal/server-utils -> @sentry/server-utils starting from v10.58.0
  • @sentry-internal/replay -> @sentry/replay starting from v10.58.0
  • @sentry-internal/replay-canvas -> @sentry/replay-canvas starting from v10.58.0
  • @sentry-internal/feedback -> @sentry/feedback starting from v10.58.0
  • @sentry-internal/typescript -> @sentry/typescript starting from v10.58.0
  • @sentry-internal/eslint-plugin-sdk -> @sentry/eslint-plugin-sdk starting from v10.58.0
  • @sentry-internal/eslint-config-sdk -> @sentry/eslint-config-sdk starting from v10.58.0
  • @sentry-internal/rrweb -> @sentry/rrweb starting from v2.43.2
  • @sentry-internal/rrweb-snapshot -> @sentry/rrweb-snapshot starting from v2.43.2
  • @sentry-internal/rrweb-types -> @sentry/rrweb-types starting from v2.43.2
  • @sentry-internal/rrdom -> @sentry/rrdom starting from v2.43.2
  • @sentry-internal/rrweb-player -> @sentry/rrweb-player starting from v2.43.2
  • @sentry-internal/rrweb-packer -> @sentry/rrweb-packer starting from v2.43.2
  • @sentry-internal/node-cpu-profiler -> @sentry/node-cpu-profiler starting from v2.4.2
  • @sentry-internal/node-native-stacktrace -> @sentry/node-native-stacktrace starting from v0.5.1

Who needs to make changes?

Most SDK users do not need to change anything. You may need to update references if you:

  • directly install one of the renamed @sentry-internal/* packages
  • import from one of those packages in code
  • pin one of those package names in a lockfile, CI config, release script, or bundler config

In those cases, update the dependency to use the @sentry/* scope and refresh your lockfile.

For example:

- "@sentry-internal/rrweb": "2.43.0"
+ "@sentry/rrweb": "2.43.2"

Why we changed this

These packages are still primarily intended for Sentry-owned SDKs and Sentry-maintained packages. Moving them under the @sentry/* scope makes package ownership clearer, removes the separate @sentry-internal npm scope from published artifacts, and keeps related SDK packages under one organization namespace.

This does not turn these packages into stable public APIs. Unless a package is documented as a public SDK package, direct usage should still be treated as internal and may change outside normal public SDK SemVer expectations.

Fetched June 15, 2026