npm upgrade
Home@sentry/opentelemetry 7 → 8
7.120.4 → 8.55.2. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@sentry/opentelemetry 8.55.2 removes or renames exports your code may import.
- Removed
- 15
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 16
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade @sentry/opentelemetry@7.120.4..8.55.2
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- OpenTelemetryScopeobject
- _INTERNALobject
- addTracingExtensionsobject
- getCurrentHubobject
- getPropagationContextFromContextobject
- getRootSpanobject
- getSpanFinishScopeobject
- getSpanHubobject
- getSpanMetadataobject
- getSpanParentobject
- getSpanScopeobject
- setHubOnContextobject
- setPropagationContextOnContextobject
- setSpanMetadataobject
- setupGlobalHubobject
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 23, 2026. @sentry/opentelemetry on lurq.