docs: improve diagnostics user journey - #131
Open
ojedaJD wants to merge 1 commit into
Open
Conversation
Expanded the user journey documentation with details on diagnostics, including steps to record before starting an investigation and options for choosing a diagnostic path based on symptoms. Signed-off-by: JD De Dios Ojeda <89946133+ojedaJD@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @nodejs/diagnostics Please review the changes when you have a chance. Thank you! 🙏 |
avivkeller
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This update helps readers understand the Node.js diagnostic process, gather useful context before investigating, and choose a diagnostic guide based on their application’s symptoms.
Validation
Related to nodejs/diagnostics#630.