What's Changed

This release makes Exceptionless much easier to adopt in modern JavaScript apps and improves the quality of the data you get back when something goes wrong.

The biggest addition is official React Native and Expo support, including automatic capture of unhandled JavaScript errors and promise rejections, persistent offline queueing, device and environment details, session tracking, and native iOS crash reporting. This gives mobile teams a much more complete picture of production issues without needing to stitch together a custom integration.

We've also improved the React experience by adding fallback support to the React error boundary and capturing React component stack information with reported errors. That means crashes are easier to surface gracefully in the UI, while the error data sent to Exceptionless is more actionable when you need to debug render failures.

For teams working in newer frameworks, we've added a simple Next.js reference integration example to make setup clearer and faster.

Under the hood, we also made reliability improvements to core utilities, including stronger random value generation and safer version parsing, along with general dependency and tooling refreshes.

Improvements

• Added official @exceptionless/react-native support for React Native and Expo
• Added native iOS crash reporting support for React Native apps
• Added a React error boundary fallback experience
• Included React component stack details in reported browser/React errors
• Added a simple Next.js integration example
• Improved core utility reliability and modernized project tooling

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

What's Changed

This release makes Exceptionless much easier to adopt in modern JavaScript apps and improves the quality of the data you get back when something goes wrong.

The biggest addition is official React Native and Expo support, including automatic capture of unhandled JavaScript errors and promise rejections, persistent offline queueing, device and environment details, session tracking, and native iOS crash reporting. This gives mobile teams a much more complete picture of production issues without needing to stitch together a custom integration.

We've also improved the React experience by adding fallback support to the React error boundary and capturing React component stack information with reported errors. That means crashes are easier to surface gracefully in the UI, while the error data sent to Exceptionless is more actionable when you need to debug render failures.

For teams working in newer frameworks, we've added a simple Next.js reference integration example to make setup clearer and faster.

Under the hood, we also made reliability improvements to core utilities, including stronger random value generation and safer version parsing, along with general dependency and tooling refreshes.

Improvements

• Added official @exceptionless/react-native support for React Native and Expo
• Added native iOS crash reporting support for React Native apps
• Added a React error boundary fallback experience
• Included React component stack details in reported browser/React errors
• Added a simple Next.js integration example
• Improved core utility reliability and modernized project tooling

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

What's Changed

We've attended to some maintenance tasks and wired up linting and formatting and upgraded dependencies while we were at it.

BREAKING

• Target ES2022 instead of ES2021 by @niemyjski in #149 Wanted to label this as breaking but we have not changed any of the API, this just gives us updated definitions like Error: clause, smaller bundles and allows us to use new features that have had plenty of time to roll out!

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

This release focused on fixing a bug (#140) where the NodeJS client could throw an error on startup when trying to configure the localStorage polyfill. This was detected when running inside of an AWS Lambda function.

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

This release focused on fixing a bug where SimpleError type was not exported.

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

This release focused on improving the experience around logging.

Improvements

• Added LogLevel type for better auto completion

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

This release focused on improving the experience around unhandledRejection errors.

Improvements

• Added additional checks for unhandledRejection errors
• Updated toError to not define an error stack when creating new error instances.
• Added ability to handle errors that have no stack

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

This release added support for capturing request info headers!

New Features

• Added support for headers by @niemyjski in #133

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

This release focused on clearing the entire JavaScript client GitHub backlog and adding awesome new capabilities! We now have a super robust prune implementation that we think it's the best implementation out there that supports all JavaScript types! This allows us to finally respect max depth when sending custom event data. We also greatly improved the client behavior to terminate gracefully if when the last app statement executes, leading to a much-improved CLI / Lambda experience.

New Features

• Fixes #42 QueueTimer keeps Node process from terminating gracefully by @niemyjski in #128
• Fixes #25 Add support for stringifying event data with a maxDepth by @niemyjski in #127
• Fixes #32 Addressed different promise rejection error types by @niemyjski in #120
• Fixes #70: Ignore errors created from browser extensions by @niemyjski in #123
• Fixes #85 Improvements to session management (Breaking Change) by @niemyjski in #124
• Export all transitive exports (from @exceptionless/core) in dependent packages. This greatly improves the developer experience and resolves issues around browser bundles and @exceptionless/core imports.
• Updated readme for Node --enable-source-maps

Bug Fixes

• Fixed issue with Configuration Default Data not getting data exclusions applied.
• Queue timer fires even when api key isn't configured by @niemyjski in #121
• Preserve event type if event has error by @niemyjski in #122
• Fixes #53 Ensure storage api calls error are caught and logged by @niemyjski in #126
• Use toError for jQuery and angular errors. This fixes issues where the client may have thrown an exception due to an invalid error type. We also added examples for various error browser integrations (e.g., jQuery).

Breaking changes

• Target ES2021 and ESM Node 18 (fetch built in) by @niemyjski in #125

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!

• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback

This is a maintenance release that improved the npm workspaces story, fixed some minor bugs and added a new SvelteKit sample app.

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!

• User Interface Feedback
• .NET Client Feedback
• JavaScript Client Feedback
• Exceptionless Feedback