v4.0.1

Changed

• Improve type definition for notify() error argument (credit @rokerkony)
• Remove process.env.NODE_ENV inferred releaseStage
• Sidestep uglify's drop_compat option to prevent it from breaking bugsnag

v4.0.0

Version 4 is a milestone release. A complete re-write and modernization for Bugsnag's JS error reporting.

See UPGRADING.md for migrating from v3 and see docs.bugsnag.com for full documentation.

🚀

v3.3.3

Bug fixes

• Ensure user-supplied severity in a callback is retained. Credit @apexskier (#276).

v3.3.2

Bug fixes

• Prevent crash when promise rejection reason is null. Credit @kchodorow (#252).

v3.3.1

Bug fixes

• Fix truncation of objects that don't inherit from Object.prototype, e.g. Object.create(null). (#263/#261)

v3.3.0

Enhancements

• Added support for detecting whether an error report was handled or unhandled. (#259)

v3.2.2

Bug Fixes

• Parse array-typed options from data-* attrs. Fixes #249. (#258)
• Log console.group and console.groupCollapsed calls as breadcrumbs. Credit @TobiasBales (#252).

v3.2.1

Bug fixes

• Fix issue when window.onerror is called with a single argument (#254)

v3.1.0

Enhancements

• Added ability to notify on unhandled promise rejection in browsers that
  support the unhandledrejection event.
  Credit: @jacobmarshall (#221)
• Added license field to package.json
  Credit: @pzrq (#214)

v3.0.7

Enhancements

• Added support for infinitely recursive metadata objects. (#200)
  Recursive metadata will be serialized up to a maximum depth, configurable by
  the Bugnsnag.maxDepth setting (default is 5).
  Credit: @omniroot, @jacobmarshall, @eanakashima
• The breadcrumb limit of 20 is now configurable up to a hard limit of 40.
  Credit: @omniroot and @eanakashima