-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] requesting comments on diagnostics-howtos project #92
Comments
Personally, I would love to get some more technical documentation in this repo, as long as it doesn't get to userland specific. As in, don't document an external tool but external references are fine. Eventually, we can consider moving it to gh-pages and finally to nodejs.org under some more advanced documentation branch. |
Suggest doc goes here: https://nodejs.org/en/docs/guides/ if it's foundation content. As above, links only if it's about external/3rd party tools. |
Earlier PR - added more information about llnode: naugtur/node-diagnostics-howtos#1 New PR adding information for node-report: naugtur/node-diagnostics-howtos#2 |
should this remain open? [ I am trying to chase dormant issues to closure ] |
I intended to keep adding more of those articles to the guides, but there's been this #254 going on while I couldn't participate (fatherly duties) I'm happy to help when I get time. Let's close this and converge on the other issue. |
I'm working on creating a more accessible introduction to diagnostics.
https://github.com/naugtur/node-diagnostics-howtos
The flame graphs section is complete in terms of content (not to be confused with finished). I'm planning to extract the exercise into a separate repository or publish i to npm in a more terminal-interactive form.
Looking forward to any comments, especially on where to put this once ready, what should be included and overall direction/goals.
The text was updated successfully, but these errors were encountered: