Exceptionless JavaScript client
We've attended to some maintenance tasks and wired up linting and formatting and upgraded dependencies while we were at it.
Please take a look at the change log for a full list of the changes.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
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.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
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.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
This release focused on improving the experience around logging.
Please take a look at the change log for a full list of the changes.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
This release focused on improving the experience around unhandledRejection errors.
unhandledRejection errorstoError to not define an error stack when creating new error instances.Please take a look at the change log for a full list of the changes.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
This release added support for capturing request info headers!
Please take a look at the change log for a full list of the changes.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
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.
@exceptionless/core) in dependent packages. This greatly improves the developer experience and resolves issues around browser bundles and @exceptionless/core imports.--enable-source-maps
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).Please take a look at the change log for a full list of the changes.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
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.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
We have put a ton of work into modernizing the JavaScript client to take advantage of the latest JavaScript features. When we first started writing the JavaScript client we could only target ES3. A lot has changed since then, so we wanted update the client to embrace the future while removing blocking issues that was preventing us from supporting newer technologies such as react native.
@exceptionless/browser npm package) !useSessions(), useReferenceIds()) that could be inferred at runtime.@exceptionless/react npm package. We've included an example application showing how easy it is to configure.@exceptionless/vue npm package. We've included an example application showing how easy it is to configure.exceptionless npm package has been deprecated. We recommend upgrading to the @exceptionless/browser or @exceptionless/node packages respectively.lastReferenceIdManager, log, storage, queue, submissionClient) into a services property and removed services (environmentInfoCollector, errorParser, moduleCollector, requestInfoCollector) that made more sense as a plugin or were no longer needed.submissionAdapter, submissionClient, useSessions(), useReferenceIds(), defaults. The client will automatically handle sessions and reference ids based on usage.addRequestInfo fluent EventBuilder API function. This was platform specific to node and didn't make sense in most cases. We replaced it with setContextProperty(key, value) which can be used to set data on the EventBuilder context to be consumed in a plugin. If you were using addRequestInfo(req) you should now call setContextProperty(KnownEventDataKeys.RequestInfo, req)
Please take a look at the change log for a full list of the changes.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!
We have put a ton of work into modernizing the JavaScript client to take advantage of the latest JavaScript features. When we first started writing the JavaScript client we could only target ES3. A lot has changed since then, so we wanted update the client to embrace the future while removing blocking issues that was preventing us from supporting newer technologies such as react native.
@exceptionless/browser npm package) !useSessions(), useReferenceIds()) that could be inferred at runtime.@exceptionless/react npm package. We've included an example application showing how easy it is to configure.@exceptionless/vue npm package. We've included an example application showing how easy it is to configure.exceptionless npm package has been deprecated. We recommend upgrading to the @exceptionless/browser or @exceptionless/node packages respectively.lastReferenceIdManager, log, storage, queue, submissionClient) into a services property and removed services (environmentInfoCollector, errorParser, moduleCollector, requestInfoCollector) that made more sense as a plugin or were no longer needed.submissionAdapter, submissionClient, useSessions(), useReferenceIds(), defaults. The client will automatically handle sessions and reference ids based on usage.addRequestInfo fluent EventBuilder API function. This was platform specific to node and didn't make sense in most cases. We replaced it with setContextProperty(key, value) which can be used to set data on the EventBuilder context to be consumed in a plugin. If you were using addRequestInfo(req) you should now call setContextProperty(KnownEventDataKeys.RequestInfo, req)
Please take a look at the change log for a full list of the changes.
We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!