Skip to content

Releases: getsentry/sentry-javascript-bundler-plugins

2.2.2

12 Jun 09:36
Compare
Choose a tag to compare
  • fix(esbuild): Don't use namespace for esbuild proxy resolving (#311)
  • fix: Update commentUseStrictRegex to be lazy instead of greedy (#309)

Work in this release contributed by @jdk2pq. Thank you for your contribution!

2.2.1

06 Jun 15:05
Compare
Choose a tag to compare
  • fix(esbuild): Inject different debug IDs into different output bundles (#301)
  • fix(webpack): Set minimum webpack 4 peer dep to 4.40.0 (#290)
  • fix: Use magic-string appendLeft instead of replace (#303)
  • ref: Improve log message when sourcemap cannot be found (#287)

2.2.0

25 May 09:29
Compare
Choose a tag to compare
  • ref(core): Make better use of Sentry (#246)
  • ref(webpack): Use webpack peer dependency (#273)

Work in this release was made possible with help from @wojtekmaj and @dobladov. Thank you for your contributions!

2.1.0

24 May 13:12
Compare
Choose a tag to compare
  • docs: Add removal of configFile option to migration guide (#266)
  • feat: Auto detect build artifacts (#257)
  • fix(core): Ignore query and hash in filepaths for release injection (#272)
  • fix(esbuild): Use absolute path for virtual file resolving (#269)
  • fix: Don't show log message if telemetry is disabled (#267)
  • fix: Use automatic release name detection for release injection (#271)

2.0.0

22 May 11:01
Compare
Choose a tag to compare

Version 2.0.0 marks the official release of the @sentry/vite-plugin, @sentry/esbuild-plugin and @sentry/rollup-plugin packages.
They are now considered stable.

For the @sentry/webpack-plugin this is a major release with breaking changes.
Please refer to the migration guide for instructions on how to upgrade.

  • feat(core): Add deleteFilesAfterUpload option (#244)
  • feat(core): Implements rewrite sources for debug ID upload (#243)
  • fix(core): Account for undefined release name values (#251)
  • fix(webpack): Inject different debug IDs for different bundles (#242)
  • ref(core): Add new options type for future use (#216)
  • ref(core): Extract debug ID injection into separate plugins (#230)
  • ref(core): Extract debug ID sourcemap upload into a separate plugin (#231)
  • ref(core): Extract release injection into separate plugins (#218)
  • ref(core): Extract release management into a separate plugin (#232)
  • ref(core): Extract telemetry into a separate plugin (#234)
  • ref(core): Switch to v2 options (#237)
  • ref(core): Use debug ID as filename for upload (#247)
  • ref(core): Use factory function to create individual plugins (#229)
  • ref: Remove injectReleasesMap option (#236)

2.0.0-alpha.7

22 May 08:24
Compare
Choose a tag to compare
2.0.0-alpha.7 Pre-release
Pre-release

This is an alpha release.

0.7.2

17 Apr 17:09
Compare
Choose a tag to compare
  • fix(core): Use createRequire to not use built-in require in ESM (#212)

0.7.1

17 Apr 15:08
Compare
Choose a tag to compare
  • fix(core): Fix vite complaining about CJS import of webpack-sources (#210)

0.7.0

17 Apr 10:54
Compare
Choose a tag to compare

This release introduces the sourcemaps option. This option switches to a new system of handling source maps in Sentry.

While the old system is still available via the include option, the recommended way forward is the sourcemaps option.

You can configure the sourcemaps option as follows:

plugin({
  org: "Your organization",
  project: "Your project",
  authToken: "Your auth token",

  sourcemaps: {
    // Specify the directory containing build artifacts
    assets: "./dist/**",
  },
});
  • feat(esbuild): Add debug ID injection for esbuild (#202)
  • feat: Promote debug ID uploading to stable via sourcemaps option (#204)
  • fix(core): Also do debug ID injection for .cjs files (#203)
  • fix: Add typing exports to packages (#208)

0.6.0

11 Apr 08:22
Compare
Choose a tag to compare
  • feat(webpack): Add debug ID injection to the webpack plugin (#198)
  • fix(core): Don't exclude release injection module (#200)
  • ref(core): Don't interact with Sentry in watch-mode (#199)

Work in this release contributed by @hakubo. Thank you for your contribution!