npm upgrade
Home@sentry/bundler-plugin-core 3 → 4
3.6.1 → 4.9.1. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@sentry/bundler-plugin-core 4.9.1 removes or renames exports your code may import.
- Removed
- 4
- Renamed
- 0
- Signature changes
- 1
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 2
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/bundler-plugin-core@3.6.1..4.9.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.
- createRollupDebugIdInjectionHooksfunction
- createRollupModuleMetadataInjectionHooksfunction
- createRollupReleaseInjectionHooksfunction
- getBuildInformationobject
Signature changes
Still exported, but the number of arguments it reads changed.
- createComponentNameAnnotateHooks1 → 2 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 19, 2026. @sentry/bundler-plugin-core on lurq.