Releases: bugsnag/bugsnag-js
Releases · bugsnag/bugsnag-js
v4.6.2
The previous version (v4.6.1) was removed from the npm registry and the CDN because of a critical issue surrounding history state methods. This release resolves that issue. The release notes for v4.6.1 are included here too for completeness.
Fixed
v4.6.1
A couple of fixes for IE10/11 relating to quirks in their implementation of the history APIs.
Fixed
v4.6.0
Added
- It is now possible to customize the logger by setting the
logger
option of the configuration object. A custom logger must have the methodsdebug
,info
,warn
anderror
. To completely disable logging, setlogger: null
. (#340)
Fixed
- A custom version of safe-json-stringify now fully protects against circular structures returned from toJSON() and arbitrarily wide/deep structures (#338)
v4.5.0
Added
- New breadcrumbs! Breadcrumbs are now left when requests are made using XMLHttpRequest (ajax) or fetch(). This works with all request libraries out of the box: jQuery, axios, superagent etc. Metadata includes HTTP method, request url and the status code (if available). By default network breadcrumbs are collected with all other autoBreadcrumb types. If you don't want to collect network breadcrumbs, set
networkBreadcrumbsEnabled: false
. (#334)
Changed
v4.4.0
Changed
- Switch from a protocol-relative default for endpoint and sessionEndpoint to "https://". IE8/9 will attempt to send via http if the protocol of the current page is http. Otherwise all requests will now go via https unless configured otherwise (#333).
Fixed
- Fix rollup bundling issue (switching to a forked version of cuid) (#331)
v4.3.1
v4.3.0
Added
- Stub exported types to appease Angular's JIT compiler in dev mode (#323)
- Make hasStack(err) check more strict, making the unhandled rejection handler more robust and useful (#322)
Changed
- Strip query strings and fragments from stackframe files (#328)
- Switch to upstream version of
fast-safe-stringify
v4.2.0
This release fixes a few issues with the fetching of inline script content, particularly after the location has changed due to window.history methods.
Unhandled promise rejection should also contain more actionable information (when the rejection reason is a DOMException
, null
, or undefined
). Support for Bluebird promises was also added.
Added
Changed
- Improved serialization of promise rejection reasons (#317)
- If a string was thrown and not caught, use it as the error message (#319)
Fixed
v4.1.3
Fixed
- Fix call to non-existent
logger.log()
(credit @alexstrat #304)
v4.1.2
Added
- Session sending now respects
notifyReleaseStages
option
Changed
- Rename option
enableSessionTracking
->autoCaptureSessions
for consistency with other platforms