User Journey tracking documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js
- Domain
- documentation
Research direction
Start in the documentation folder and review issue #439 for the tutorials produced by the WG Deep Dive. Choose an unchecked tutorial from the list, following the linked llnode issue where relevant, and update this issue when the tutorial is completed. Done means the selected tutorial is transposed into a live document and its checklist entry is marked complete.
Written by the indexing model from the issue text.
Description
This issue aims to track the remaining tutorials under documentation folder.
The https://github.com/nodejs/diagnostics/issues/439 contains the documents created in the WG Deep Dive and we are working to transpose them into live documents.
- Abnormal Termination
- Using exit stack traces
- Using diagnotics report
- Using valgrind
- Using llnode
- CPU
- Monitoring Excessive CPU Usage
- Crash
- What is a crash (intro)
- Using node report
- Using llnode (https://github.com/nodejs/llnode/issues/401)
- Hang
- Using trace sigint
- Using Chrome DevTools
- Using node report
- Live Debugging (https://github.com/nodejs/nodejs.org/pull/4772)
- Using Node Inspector
- Memory (https://github.com/nodejs/nodejs.org/pull/4728)
- Using Heap Profiler
- Using Heap Snapshot
- Using GC Traces
- Using Native Tools
- Poor Performance (https://github.com/nodejs/nodejs.org/pull/4928)
- Using V8 Profiler
- Using Linux Perf
- Tracing
- Using Trace Events
Feel free to update this description when a tutorial is done.
cc: @nodejs/diagnostics
- Dominant language
- No language data
- Stars
- 550
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 nodejs/diagnostics
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
nodejs/diagnostics#648 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
nodejs/diagnostics#690 · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
nodejs/diagnostics#689 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
nodejs/diagnostics#688 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
nodejs/diagnostics#687 ·
All issues in nodejs/diagnostics
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100