bugsnag-js

Added

• Support serialising error objects (via. @bugsnag/[email protected]) (#356, #458)

Fixed

• Fixed granular breadcrumb config logic (#461, #465, #466)

Fixed

• Support @bugsnag/node being consumed in a Webpack bundle for Node (#450, #441)

Fixed

• Tolerate errors accessing properties of an unhandled rejection event (#394, #442)
• Improve robustness of window.onerror callback, supporting additional jQuery parameter (#443, fixing #393 and #392)
• Add CORS header Access-Control-Allow-Origin: * to uploaded S3 assets (#444)

Fixed

• Ensure objects with a null prototype or bad toString() implementation don't cause an error in console breadcrumbs (#429)
• Ensure user ip is not collected when collectUserIp=false but user.id is explicitly undefined (#428)
• Ensure previous window.onerror callback is always called (#427)
• Ensure previous window.onreadystatechange callback is called (#426)
• Ensure log methods are correctly called and that relevant callbacks are called in the event of a report failure (#437)

Added

• Nuxt.js example (#425)

This is the first release of Bugsnag notifiers under the @bugsnag namespace.

This "universal" repository combines Bugsnag's browser and Node.js notifiers and so for continuity with the browser version, which was at v4, the starting point for this monorepo and all of its packages is v5.0.0.

See UPGRADING.md for guidance on how to update your application.

Removed

• Stop sending stacktrace with breadcrumb metadata

Fixed

• Added missing instance properties to Breadcrumb TypeScript definition

Fixed

• Workaround for iOS9 Safari CSP issue which caused bugsnag-js to throw an error (#358, #357)

This release fixes a couple of bugs with stacktrace parsing.

Fixed

• Incorrect parsing of stacktraces for errors in Chrome that have no stackframes (#355)
• Incorrect parsing of stacktraces for errors in Firefox/Safari that have "@" in the URL path (#354)

Note: this release alters the behaviour of the notifier to track sessions automatically.

As part of this change, the way in which URLs are configured has been updated:

- endpoint: 'https://bugsnag-notify.example.com',
- sessionEndpoint: 'https://bugsnag-sessions.example.com',
+ endpoints: {
+  notify: 'https://bugsnag-notify.example.com',
+  sessions: 'https://bugsnag-sessions.example.com'
+ }

endpoint and sessionEndpoint are now deprecated but still supported. Note that session tracking will be disabled if the notify endpoint is configured but the sessions endpoint is not – this is to avoid inadvertently sending session payloads to the wrong server.

Added

• A new end-to-end/black box test suite has been added (#351)

Changed

• autoCaptureSessions default value was false and is now true (#341)

Deprecated

• endpoint and sessionEndpoint have been deprecated and combined into a single new option: endpoints (#341)

Removed

• The old e2e test suite has been removed (#351)

Fixed

• Use the correct network breadcrumb type (network -> request). Fixes network breadcrumbs not displaying in the dashboard. (#348)

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

• Fix history API url parameter logic (#347)
• Only pass in url parameter to history methods when it is not undefined. Fixes a bug in IE11 where it converts undefined to a string, causing a redirect to /undefined. (#342)
• Prevent a crash in IE10 when accessing history.state. (#345)

A couple of fixes for IE10/11 relating to quirks in their implementation of the history APIs.

Fixed

• Only pass in url parameter to history methods when it is not undefined. Fixes a bug in IE11 where it converts undefined to a string, causing a redirect to /undefined. (#342)
• Prevent a crash in IE10 when accessing history.state. (#345)

Added

• It is now possible to customize the logger by setting the logger option of the configuration object. A custom logger must have the methods debug, info, warn and error. To completely disable logging, set logger: 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)

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

• As part of #334 envify was added to compile out plugin "destroy" logic that was only required for tests.

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)

Changed

• Perf improvements for breadcrumbs, most notably console log methods with lots of data (#329)

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

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

• Support for unhandled bluebird promise rejections (#317)
• Option to prevent IP collection (#313)

Changed

• Improved serialization of promise rejection reasons (#317)
• If a string was thrown and not caught, use it as the error message (#319)

Fixed

• Collection of inline script content improved (#320, #318)

Fixed

• Fix call to non-existent logger.log() (credit @alexstrat #304)

Added

• Session sending now respects notifyReleaseStages option

Changed

• Rename option enableSessionTracking -> autoCaptureSessions for consistency with other platforms