Repository navigation
feat: Export the Node bundler plugins from SDKs that wrap @sentry/node - #25536
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit e8374ad. Configure here.
size-limit report 📦Compared: 053f6c6 (PR test merge using develop at 8042719) Against: 8042719 (develop) · base run #63102 ✅ Baseline matches: this diff contains only this PR's changes.
|
Optional E2E testsSome optional checks were not successful. They do not block the merge. 1 failing, 57 successful. See the run.
Successful checks
|
s1gr1d
left a comment
There was a problem hiding this comment.
Looks good in general, but should we rather add a E2E test variant for using e.g. the sentryWebpackPlugin? Because other than the webpack.config.js file, everything else is quite the same. Just to make sure that the test apps don't drift apart too much.

Adds
@sentry/nestjs/webpackand@sentry/aws-serverless/esbuild, which re-export the matching@sentry/nodeplugins. The Nest CLI only bundles with webpack, and Lambda deploy tools such as CDK, SAM and the Serverless Framework bundle with esbuild, so these are the two entry points users of those SDKs need. Users no longer need@sentry/bundler-pluginsas an extra dependency.@sentry/google-cloud-serverless,@sentry/honoand@sentry/effectget no entry points. Cloud Functions deploys rarely bundle, Hono would also need Cloudflare entries, and Effect builds also target the browser.Fixes #25522