-
-
Notifications
You must be signed in to change notification settings - Fork 37.2k
"Just My Code" for stack traces? #20505
Copy link
Copy link
Closed
Labels
discussIssues opened for discussion and feedback.Issues opened for discussion and feedback.errorsIssues and PRs related to JavaScript errors originating in Node.js core.Issues and PRs related to JavaScript errors originating in Node.js core.promisesIssues and PRs related to ECMAScript promises.Issues and PRs related to ECMAScript promises.
Description
Activity
Metadata
Metadata
Assignees
Labels
discussIssues opened for discussion and feedback.Issues opened for discussion and feedback.errorsIssues and PRs related to JavaScript errors originating in Node.js core.Issues and PRs related to JavaScript errors originating in Node.js core.promisesIssues and PRs related to ECMAScript promises.Issues and PRs related to ECMAScript promises.
Throwing a raw idea out there:
I just saw this question where a user was confused about a stack trace they got when using puppeteer:
The point is, the first few stack frames are irrelevant to the user. If the first stack frame showed the part in their code that caused the error it would have been a lot more useful.
I'm wondering if we can improve the debugging experience of users by giving them "Just My Code"
Just My Code
Node could expose a "Just My Code" exception mode similar to the way stacks work in the Chrome devtools. Running Node with the flag would hide any frames from
node_modulesfolder.Thoughts?