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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Add node-report to cdp and add Visual Panel like React or Vue #27858
Comments
cc @nodejs/diagnostics |
Also in both cases, where does the feature be developed? in core, or in chrome? can the |
|
Nope, my thought is a new panel, like opened in
Hopefully work on Node.js with |
TBH I don't know how much value it is to show the JSON data that node-report or diagnostic-report provides in a DevTools panel, visually.. |
Kind of like DOM in front end ( |
@gengjiawen Will likely drop in the next version of NiM(see screenshot from the DevTools Panel)... Will have the ability to save reports and quickly access reports from multiple node instances. Stay tuned. |
Took over a week to get the update pushed thru the Chrome Web Store but it is done. https://blog.brakecode.com/nodejs-diagnostic-reports/ |
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
I found node-report is very usefully (tbh I am a little surprised that Node.js has this level of clarity, really amazing job 馃憤 ), in some cases more usefully than profiler :)
I would like two thing:
kind of like this (pic from https://github.com/vuejs/vue-devtools), but for
node-report
kind of like https://chromedevtools.github.io/devtools-protocol/tot/SystemInfo, but we add it only in Node domain https://chromedevtools.github.io/devtools-protocol/v8.
cc @nodejs/inspector @nodejs/report @richardlau
(Not sure I ping the group right, I don't know the Node.js group category )
The text was updated successfully, but these errors were encountered: