npm upgrade
Home@sentry/node 8 → 9
8.55.2 → 9.47.1. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@sentry/node 9.47.1 removes or renames exports your code may import.
- Removed
- 11
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 19
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/node@8.55.2..9.47.1
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.
- DEFAULT_USER_INCLUDESobject
- addOpenTelemetryInstrumentationobject
- addRequestDataToEventobject
- debugIntegrationobject
- extractRequestDataobject
- getCurrentHubobject
- metricsobject
- nestIntegrationobject
- processThreadBreadcrumbIntegrationobject
- sessionTimingIntegrationobject
- setupNestErrorHandlerobject
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 28, 2026. @sentry/node on lurq.