BetterJS/badjs-report
Badjs Report
Badjs-report is a client-side JavaScript library designed to capture, manage, and report runtime exceptions and telemetry data from web applications to a remote server. It functions as a diagnostic framework that automatically intercepts global errors and wraps asynchronous operations to ensure that issues are tracked without requiring manual instrumentation throughout the codebase.
The library distinguishes itself through its focus on traffic optimization and data reliability. It employs deduplication logic to suppress redundant error reports and applies probabilistic sampling to manage the volume of diagnostic data sent to the server. To ensure data integrity during unstable network conditions, the library utilizes local storage to queue reports, automatically synchronizing them once connectivity is restored.
Beyond core exception tracking, the library supports the logging of custom events and user activity. This allows for the collection of contextual information alongside error reports, providing visibility into application state and performance during the development or production lifecycle.
Features
- Frontend Monitoring Tools - Captures and reports client-side JavaScript exceptions to a remote server to help developers identify and fix production bugs.
- JavaScript Error Trackers - Intercepts global errors and asynchronous callbacks to provide visibility into runtime issues within web applications.
- Global Exception Handlers - Hooks into the runtime error handler to automatically capture unhandled exceptions and stack traces without requiring manual instrumentation.
- Diagnostic - Applies configurable rate-limiting logic to incoming error streams to manage server load and reduce data volume during high-traffic events.
- Client-Side Deduplication - Analyzes error signatures in memory to suppress redundant reports and minimize network traffic before sending data to the server.
- Asynchronous Callback Wrappers - Wraps native timer and promise functions to inject error-catching logic into the execution flow of asynchronous application code.
- Asynchronous Error Handling - Wraps callbacks and third-party library methods to ensure that errors occurring within asynchronous operations are captured and reported reliably.
- Asynchronous Exception Wrappers - Wraps third-party library methods and asynchronous callbacks to ensure exceptions occurring within these specific contexts are caught and reported correctly.
- Application Logging - Tracks custom events and user activity logs alongside error reports to provide context for debugging complex application state issues.
- Automatic Error Logging - Intercepts global application errors automatically to report diagnostic information to a remote server without requiring manual try-catch blocks.
- Offline Error Queues - Stores error reports on the local device when the network is unavailable and automatically synchronizes them to the server once connectivity is restored.
- Error Reporting - Reduces noise by deduplicating identical error reports and applying sampling rates to control the total volume of data sent to the monitoring server.
- Diagnostic Traffic Controllers - Manages the volume of diagnostic data by deduplicating identical errors and applying sampling rates to optimize server-side monitoring costs.
- Telemetry Collectors - Provides a data collection framework that manages error reporting volume through deduplication and sampling to optimize network traffic and server load.
- Browser Local Storage Management - Persists diagnostic data in browser storage to ensure error reports survive page reloads and network outages before eventual synchronization.
- Offline Synchronization - Stores error data locally during network outages and automatically transmits logs once connectivity is restored.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
