Skip to content

Releases: exceptionless/Exceptionless.JavaScript

v1.4.0

10 May 21:04

Choose a tag to compare

Version 1.4.0 focused on improvements to sessions, real time configuration and logging.

  • Added the ability to exclude events by type and source in real time as well as minimum log levels! We've made improvements to real time project configuration to ensure that if you accidentally disable logging completely, your settings can be updated in the background and functionality restored! We will expand on UI support for this in the near future, in the mean time please check out the example project configuration below:
    • Key: @@EVENT_TYPE:SOURCE Value: false You can use any event type or source. We support using wildcards * as part of the source. If you want to ignore complete event types then set the source to *.
    • Key: @@error:*MyCustomException Value: false The following disables the submission of any error event where the stack trace contains an exception with a type name that ends with MyCustomException. You can also specify the full type name with namespace and remove the wildcard.
    • Key: @@log:* Value: Off Log types are special cased but still accept true or false for values. This example will turn off log messages completely. Known values are: Trace, Debug, Info, Warn, Error, Fatal, Off.
    • Key: @@log:MyNamespace.EventPostsJob Value: Info This sets a minimum log level for the EventPostsJob.
  • Added support for automatically checking for updated configuration settings when the client is idle. By default the client will now check every 2 minutes after the last event submission for updated configuration settings. You can also turn off the automatic updating of configuration settings when idle by calling client.config.updateSettingsWhenIdleInterval = -1;.
    • Checking for updated settings doesn't count towards plan limits.
    • Only the current configuration version is sent when checking for updated settings (no user information will ever be sent).
    • If the settings haven't changed, then no settings will be retrieved.
  • Session Heartbeats and Session End events are now sent through an optimized api end point. This means that they no longer count towards your plan limits!
  • Fixed an issue with passing settings to a new instance of ExceptionlessClient (@csantero).
  • Improved the stacking of angular response errors.

Please take a look at the change log for a full list of the changes.

Feedback

We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!

v1.3.2

26 Feb 16:56

Choose a tag to compare

Version 1.3.2 focused on added support for offline storage, manual stacking and improvements to the angular integration.

Please take a look at the change log for a full list of the changes.

Feedback

We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!

v1.3.1

25 Jan 22:53

Choose a tag to compare

This release made sessions opt in.

  • Users can now opt into sessions by setting a default user and calling exceptionless.ExceptionlessClient.default.config.useSessions();.

Please take a look at the change log for a full list of the changes.

Feedback

We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!

v1.3.0

18 Jan 23:33

Choose a tag to compare

This release focused on sessions and minor bug fixes.

  • Added ability to set a default user `exceptionless.ExceptionlessClient.default.setUserIdentity("id", "friendly name").
  • Added the ability to keep track of user sessions (a heartbeat will be sent every 30 seconds for browser users).
  • Added the ability to link events together via a new EventBuilder method called setEventReference.

Please take a look at the change log for a full list of the changes.

We'd like to take a moment to thank @frankebersoll and the community for your help with this release.

Feedback

We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!

v1.2.0

25 Nov 02:28

Choose a tag to compare

This release focused on features like capturing module info and extra error properties.

  • Added support for deduplicating JavaScript errors (#9 @frankebersoll).
  • Added support for collecting extra exception data (@frankebersoll).
  • Added support for collecting Node module info (#6 @frankebersoll).
  • Fixed an issue where Data Exclusions could cause events to be submitted in an invalid state.

Please take a look at the change log for a full list of the changes.

We'd like to take a moment to thank @frankebersoll and the community for your help with this release.

v1.1.1

22 Oct 14:31

Choose a tag to compare

This release fixed a single bug that was causing configuration settings to not be updated on IE and Edge browsers (#23).

Please take a look at the change log for a full list of the changes.

v1.1.0

20 Oct 22:13

Choose a tag to compare

This release focused on bug fixes, improving the node client and documentation.

  • Improved readme and wiki #31 (Credit @frankebersoll)
  • Fixed a bug where unhandled exceptions in Node.js were not being captured #30 (Credit @frankebersoll)
  • Fixed a bug were data exclusions were not always working #28 (Credit @srijken)
  • Temporary disabled the capturing of ajax errors #26
  • Fixed a bug where the cancelled state wasn't properly passed through the SubmitEvent callback.

Please take a look at the change log for a full list of the changes.

We'd like to take a moment to thank @frankebersoll, @srijken and the community for your help with this release.

v1.0.1

10 Aug 14:12

Choose a tag to compare

This release focused on improving the documentation, adding tests and improving error stack parsing.

  • Add self hosted documentation section and a new wiki.
  • Upgraded to the latest version of TraceKit. Which is now unit tested and has many improvements/bug fixes for parsing cross browser stack traces.
  • Added SettingsManager unit tests.

Please take a look at the change log for a full list of the changes.

v1.0.0

09 Jun 17:55

Choose a tag to compare

We've put a ton of work into the JavaScript and node clients to ensure you can capture even more errors and events. We wanted to provide you with an awesome client that gives you the full fidelity of our other error clients.

  • Client supports JavaScript and Node (Works everywhere)
  • Send your errors, logs or feature usages to your Exceptionless dashboard
  • Supports various module formats such as es6 (SystemJS/jspm), UMDRequireJS, CommonJS, or global
  • We built the Exceptionless JavaScript/Nodes.js Client with the past and future browsers in mind. Everything is testable via components injected on startup (via dependency injection), which means you can replace any component of the system to fit your specific needs.
  • Includes first class integration for third party libraries like AngularJS and Express
  • Client is a full feature parity of our .NET clients, including:
    • Support for custom objects
    • Mark events as critical
    • Server side settings
    • Data exclusions
    • Plugins
    • and more...

Usage, Examples, and more...

Everything you need to get up and running (including contributing/developing) can be found in the readme. Javascript, Express, TypeScript, SystemJS, and RequireJS examples can be found in the example folder.

Feedback

We're listening and we'd love to hear your feedback! Please send us your feedback via an in-app message for help, or submit an issue on GitHub with bugs, feedback, etc. We're here to make sure you get things working properly so you can take full advantage of Exceptionless!

v0.9.1

08 Jun 22:39

Choose a tag to compare

This release is considered a release candidate. Please give us your feedback by creating a new issue.

  • Fixed an issue where IE11 could submit an error that couldn't be deserialized server side.
  • Fixed an issue where the angular integration wasn't properly passing the log parameters.
  • Fixed an issue where createLog and submitLog overloads didn't properly handle null sources.

Please take a look at the change log for a full list of the changes.