Skip to content

Fix typos and wording in migration guide #956

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
andreiborza merged 2 commits into from
Oct 20, 2026
Merged

Fix typos and wording in migration guide #956

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b9dbfc8
docs: fix typos and grammar in migration guide
dhruvatr Oct 19, 2026
640c280
chore: Fix formatting
sentry-junior[bot] Oct 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions MIGRATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ This document serves as a migration guide, documenting all breaking changes betw

## Upgrading from 1.x to 2.x (Webpack Plugin Only)

Version 2 of `@sentry/webpack-plugin` is a complete rewrite of version 1, relying on bundler-agnostic code (based on [unjs/unplugin](https://github.com/unjs/unplugin)). While we tried to keep changes to v1 of the webpack plugin minimal, a adjustments are nevertheless necessary:
Version 2 of `@sentry/webpack-plugin` is a complete rewrite of version 1, relying on bundler-agnostic code (based on [unjs/unplugin](https://github.com/unjs/unplugin)). While we tried to keep changes to v1 of the webpack plugin minimal, a few adjustments are nevertheless necessary:

### Initialization and Required Values

Expand All @@ -41,8 +41,7 @@ sentryWebpackPlugin({

### Removal of `include` for `sourcemap` option

The `include` option was removed in favour of the new `sourcemaps` option. If you cannot migrate to the `sourcemaps`, `include` is still avaliable as the `uploadLegacySourcemaps` option.

The `include` option was removed in favour of the new `sourcemaps` option. If you cannot migrate to the `sourcemaps` option, `include` is still available as the `uploadLegacySourcemaps` option.
Use the `sourcemaps.assets` and `sourcemaps.ignore` options to indicate to the plugin which sourcemaps should be uploaded to Sentry. The plugin now also exposes `sourcemaps.deleteAfterUpload` to delete your sourcemaps after they have been uploaded to Sentry. With the `sourcemaps` options, you no longer need to set filename transforms like `urlPrefix` because the plugin uses a new debug IDs system to associate sourcemaps to your bundles.

```js
Expand Down
Loading