mafintosh / mafintosh/why-is-node-running
Is it possible to have more context?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
I'm getting four Timer results back all in promise library internals. Its pretty unclear to me how these are related to my promise library. Is it possible to have more stack-context around these entries? If there was, I'd be able to see much more clearly where these things are coming from.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the tool reports Timer results from promise library internals; the payload does not identify a source file or test. The change is complete when those entries include enough stack context for users to identify where they originated, with coverage for the reported Timer case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100