csnover/TraceKit

TraceKit will get an undefined error type and message on Unhandle Promise rejection error

Open

#84 opened on Jan 27, 2021

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (1,017 stars) (174 forks)batch import
enhancementfeature requesthelp wanted

Description

pls see images.

Screenshot from 2021-01-27 22-03-06 Screenshot from 2021-01-27 22-00-41

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
JavaScriptPromises
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate how TraceKit handles unhandled promise rejections in browsers. Look at the source code in tracekit.js, specifically the ` onUnhandledRejection` function or equivalent, to see how it extracts error type and message from the PromiseRejectionEvent. The screenshots indicate that the error type and message are undefined, which may be due to incorrect property access (e.g., `event.reason` instead of `reason`). Check for any existing comments in the issue for further clues.