Conversation
…try point The webpack plugin no longer goes through a factory that takes BannerPlugin/DefinePlugin classes; it reads them from compiler.webpack and only falls back to the installed webpack module for 5.0.x. The @sentry/bundler-plugins/webpack5 entry point is now a deprecated alias of @sentry/bundler-plugins/webpack.
…try point The webpack plugin no longer goes through a factory that takes BannerPlugin/DefinePlugin classes as a fallback for webpack < 5.1; it reads them from compiler.webpack only, so the webpack peer dependency is now >=5.1.0. The @sentry/bundler-plugins/webpack5 entry point, which exported the same plugin without that fallback, is removed.
# Conflicts: # CHANGELOG.md # packages/bundler-plugins/src/webpack/index.ts # packages/bundler-plugins/src/webpack/webpack5.ts # packages/bundler-plugins/test/webpack/public-api.test.ts # packages/bundler-plugins/test/webpack/webpack5.test.ts
timfish
marked this pull request as ready for review
September 17, 2026 11:16
Contributor
size-limit report 📦
|
chargome
approved these changes
Sep 18, 2026
|
|
||
| Work in this release was contributed by @psh4607, @thijsw, @trinitiwowka, @nehaprasad-dev, @JealousGx, @Jxxunnn, @eddie333016, @davidmurdoch, @yashschandra, @atharv-sys32, @AG0708, @birkskyum, @mkly, @mcbbugu, @suhailopensource, @zkasuran, @mohd-akram, @RealBhupesh, @halillusion, @psang39, @hafzism, @JosephDoUrden, @Tyagiquamar, @Andarist, and @msnelling. Thank you for your contributions! | ||
|
|
||
| - ref(bundler-plugins)!: The webpack plugin now requires webpack 5.1 or newer and reads its plugin classes from `compiler.webpack` only, so the `webpack` peer dependency is now `>=5.1.0`. The `@sentry/bundler-plugins/webpack5` entry point was removed; import `sentryWebpackPlugin` from `@sentry/bundler-plugins/webpack` instead, which exports the same plugin. |
Member
There was a problem hiding this comment.
Suggested change
| - ref(bundler-plugins)!: The webpack plugin now requires webpack 5.1 or newer and reads its plugin classes from `compiler.webpack` only, so the `webpack` peer dependency is now `>=5.1.0`. The `@sentry/bundler-plugins/webpack5` entry point was removed; import `sentryWebpackPlugin` from `@sentry/bundler-plugins/webpack` instead, which exports the same plugin. |
I think we can skip this entry
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The webpack plugin still carried its webpack 4 era structure: a
sentryWebpackPluginFactorythat tookBannerPlugin/DefinePluginclasses so the same code could serve webpack 4 and 5, arequire('webpack')at module load to feed those fallbacks, and a separatewebpack5entry point whose only difference was calling that factory without them. Webpack 4 hasn't been supported for a long time.The plugin now reads the classes from
compiler.webpackonly, so the factory and the fallback are gone.compiler.webpackwas added in webpack 5.1.0, three days after 5.0.0, so thewebpackpeer dependency moves to>=5.1.0. With the fallback gone there is nothing left to distinguish@sentry/bundler-plugins/webpack5from@sentry/bundler-plugins/webpack, so thewebpack5entry point is removed rather than deprecated. Both changes are documented in the v11 migration guide.