From 2ff6c7e5236cd29ab7f47019e7dacd01c5af4038 Mon Sep 17 00:00:00 2001 From: Chengzhong Wu Date: Tue, 1 Apr 2025 13:33:04 +0100 Subject: [PATCH] doc: classify Chrome DevTools Protocol as tier 2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Chrome DevTools Protocol is the de-facto debugger protocol for Node.js and is tested regularly in Node.js test suite / CI. It matches the tier 2 classification but lacks proper documentation in Node.js. Classify the Chrome DevTools Protocol as tier 2 with a target of tier 1 once we have proper documentation on stable protocols. On the other hand, the Chrome DevTools Frontend is not shipped with Node.js and not tested in Node.js CI. So keep it as tier 3. PR-URL: https://github.com/nodejs/node/pull/57634 Reviewed-By: Yagiz Nizipli Reviewed-By: Marco Ippolito Reviewed-By: Matteo Collina Reviewed-By: Tobias Nießen Reviewed-By: Luigi Pinca Reviewed-By: Darshan Sen Reviewed-By: Rafael Gonzaga Reviewed-By: Moshe Atlow --- .../diagnostic-tooling-support-tiers.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/contributing/diagnostic-tooling-support-tiers.md b/doc/contributing/diagnostic-tooling-support-tiers.md index f92a5242b7b..c8d07907c02 100644 --- a/doc/contributing/diagnostic-tooling-support-tiers.md +++ b/doc/contributing/diagnostic-tooling-support-tiers.md @@ -100,9 +100,9 @@ The tools are currently assigned to Tiers as follows: ## Tier 2 -| Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js | Target Tier | -| --------- | ------------- | ----------------------------- | ----------------------- | ----------- | -| | | | | | +| Tool Type | Tool/API Name | Regular Testing in Node.js CI | Integrated with Node.js | Target Tier | +| --------- | ---------------------------- | ----------------------------- | ----------------------- | ----------- | +| Debugger | [Chrome DevTools Protocol][] | Yes | Yes | 1 | ## Tier 3 @@ -114,7 +114,7 @@ The tools are currently assigned to Tiers as follows: | Profiling | V8 --interpreted-frames-native-stack | Yes | Yes | 2 | | Profiling | [Linux perf][] | Yes | Partial | 2 | | Profiling | [node-clinic][] | No | No | 3 | -| Debugger | [Chrome Dev tools][] | No | No | 3 | +| Debugger | [Chrome DevTools Frontend][] | No | No | 3 | ## Tier 4 @@ -129,15 +129,15 @@ The tools are currently assigned to Tiers as follows: | Memory | V8 heap profiler | No | Yes | 1 | | Memory | V8 sampling heap profiler | No | Yes | 1 | | AsyncFlow | [Async Hooks (API)][] | ? | Yes | 1 | -| Debugger | V8 Debug protocol (API) | No | Yes | 1 | | Debugger | [Command line Debug Client][] | ? | Yes | 1 | | Tracing | [trace\_events (API)][trace_events (API)] | No | Yes | 1 | | Tracing | trace\_gc | No | Yes | 1 | [0x]: https://github.com/davidmarkclements/0x [Async Hooks (API)]: https://nodejs.org/api/async_hooks.html -[Chrome Dev Tools]: https://developer.chrome.com/docs/devtools/ -[Command line Debug Client]: https://nodejs.org/api/inspector.html +[Chrome DevTools Frontend]: https://developer.chrome.com/docs/devtools/ +[Chrome DevTools Protocol]: https://chromedevtools.github.io/devtools-protocol/ +[Command line Debug Client]: https://nodejs.org/api/debugger.html [Linux perf]: https://perf.wiki.kernel.org/index.php/Main_Page [diagnostic report]: https://nodejs.org/api/report.html [node-clinic]: https://github.com/clinicjs/node-clinic/