Extract meaning from JS Errors
No description provided.
Issues mentioned in `README` should be solved by other approaches: - `.addEventListener()` is blazing fast and is not a real performance issue - to solve issues with ordering in case when regular DOM event propogation is not available consider to use thi
React Freeze
return list of CallSite objects from a captured stacktrace
Framework-agnostic, micro-library for getting stack traces in all environments
Stack Layout Component for Victory
A collection of standard object serializers for Pino
Get callsites from the V8 stack trace API
Better Stack Node.js logger (formerly Logtail)
Curated collection of data structures for the JavaScript/TypeScript.
TypeScript definitions for stack-trace
An extendable Error class that actually works, with TypeScript definition files, supporting old and new style classes and compatibility even with the oldest browsers
Simple JS queue with auto run for node and browsers
Server Web Workers for node.js that work
Better Stack logging core (formerly Logtail)
Turn AWS CloudFormation templates into AWS CDK applications
Better Stack Typescript types (formerly Logtail)
Stack traces as an array of stack frames with source maps support.
Utility for working with stack traces
Better Stack Pino transport (formerly Logtail)
A native Node.js module that can capture JavaScript stack traces from main and worker threads, even with blocked event loops.
Comlink Alternative. Built with JSON-RPC.
Simple JS queue with auto run for node and browsers