Debugging
@CrabDude is already working on this.
Since May 5, 2015.
Assessment
This issue has not been assessed yet.
Description
- Show how to log stack traces
- Always keep original error:
node promise.catch(e => { let error = new Error('Authentication failed') error.originalError = e }) - And use long stack traces both longjohn and bluebird's
- Show how to use node-inspector (node & babel-node)
debugger;--debug & --debug-brk- Recommend step debugging boxed in IDEs
- node-profiler
- node-webkit-agent
- node-block for watching event-loop latency
- nodetime
- new relic
What success looks like: Succinctness and clarity. Less is more.
Reference Wikis: Authentication & Authorization, Setup
Open separate issues for required links to community sources if you're having trouble finding any.
Please assign to yourself before working on this.
/cc @NinjaSudo @philster @azoff @DiyahM
- Dominant language
- No language data
- Stars
- 74
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
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.
More from codepath/nodejs_guides
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
codepath/nodejs_guides#21 · 1 comment ·
-
enhancement
codepath/nodejs_guides#19 · 1 comment · 1 assignee ·
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
codepath/nodejs_guides#18 · 3 comments ·
-
Design Patterns Openhelp wanted
codepath/nodejs_guides#16 · 1 assignee ·
-
help wanted
codepath/nodejs_guides#14 · 1 assignee ·