Skip to content

Releases: bugsnag/webpack-bugsnag-plugins

v1.8.0

08 Jul 08:53
0f124bd
Compare
Choose a tag to compare
  • Use webpack for logging (#55)
  • Upgrade build reporter to latest version (#57)

v1.7.0

18 May 14:17
Compare
Choose a tag to compare
  • Update to v2 of @bugsnag/source-maps (#53)

v1.6.0

17 Dec 16:20
Compare
Choose a tag to compare

v1.5.0

10 Dec 16:30
Compare
Choose a tag to compare
  • Upgrade to new @bugsnag/source-maps library (#48)

v1.4.3

28 Jan 15:02
Compare
Choose a tag to compare
  • Allow setting of codeBundleId on BugsnagSourceMapUploaderPlugin (#40, fixes #38)

v1.4.2

10 Sep 09:08
Compare
Choose a tag to compare

Changed

  • Allow publicPath to be an empty string (supports targeting Node and using the top level project directory for the output) (#39)

v1.4.1

12 Aug 10:44
Compare
Choose a tag to compare

Fixed

  • Manually join paths rather than using url.resolve() as that doesn't work with the (*) wildcard character (#37, fixes #35)

v1.4.0

13 Mar 14:37
Compare
Choose a tag to compare

Changed

  • Switch to manually calculating full paths on disk, preparing for the removal of existsAt in Webpack v5. This fixes a bug when output.futureEmitAssets is enabled in Webpack v4.29 (#29, fixes #28)

v1.3.0

21 Jan 10:59
Compare
Choose a tag to compare

Added

  • Add a list of ignored bundle exceptions (defaults to [ '.css' ], preventing CSS bundles and source maps from unnecessarily being uploaded) (#26, fixes #24)

Changed

  • Improve bundle source file lookup (when bundles are output to a different directory than their source maps) (#27, fixes #20)

v1.2.4

14 Dec 16:21
Compare
Choose a tag to compare

Fixed

  • Handle missing asset when source map is not written to disk (#23, fixes #18)