From 265e37dfc2ec4b8f6ecec7ee63a812b8f5c1dcd7 Mon Sep 17 00:00:00 2001 From: Efe Karasakal Date: Tue, 4 Nov 2025 22:16:44 +0100 Subject: [PATCH 1/5] docs(learn): improve debugging docs --- .../pages/en/learn/getting-started/debugging.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/apps/site/pages/en/learn/getting-started/debugging.md b/apps/site/pages/en/learn/getting-started/debugging.md index d68bdbe6322ef..febb04514b382 100644 --- a/apps/site/pages/en/learn/getting-started/debugging.md +++ b/apps/site/pages/en/learn/getting-started/debugging.md @@ -71,13 +71,18 @@ Several commercial and open source tools can also connect to the Node.js Inspect ### Chrome DevTools 55+, Microsoft Edge -- **Option 1**: Open `chrome://inspect` in a Chromium-based - browser or `edge://inspect` in Edge. Click the Configure button and ensure your target host and port - are listed. -- **Option 2**: Copy the `devtoolsFrontendUrl` from the output of `/json/list` - (see above) or the --inspect hint text and paste into Chrome. +#### Option 1: Use the built-in DevTools UI -See https://github.com/ChromeDevTools/devtools-frontend, https://www.microsoftedgeinsider.com for more information. +- Open `chrome://inspect` (`edge://inspect` in Microsoft Edge) in your browser. +- Click the Configure button and ensure your target host and port are listed. +- Your Node.js application should appear in the Remote Target list. + +#### Option 2: Connect manually + +- Visit `http://localhost:/json/list`. It should return a JSON object containing a `devtoolsFrontendUrl`. +- Paste the URL directly into your browser's address bar + +See [Chrome DevTools Frontend](https://github.com/ChromeDevTools/devtools-frontend) and [Microsoft Edge DevTools Guide](https://learn.microsoft.com/microsoft-edge/devtools-guide-chromium/) for more information. ### Visual Studio Code 1.10+ From 9b7a593bbea3cffebad15a21efe86d49667e2455 Mon Sep 17 00:00:00 2001 From: Efe Karasakal Date: Tue, 4 Nov 2025 22:26:14 +0100 Subject: [PATCH 2/5] docs(learn): remove gitpod section --- apps/site/pages/en/learn/getting-started/debugging.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/apps/site/pages/en/learn/getting-started/debugging.md b/apps/site/pages/en/learn/getting-started/debugging.md index febb04514b382..5e8ac5ab1b498 100644 --- a/apps/site/pages/en/learn/getting-started/debugging.md +++ b/apps/site/pages/en/learn/getting-started/debugging.md @@ -109,18 +109,12 @@ See https://github.com/microsoft/vscode for more information. See https://github.com/cyrus-and/chrome-remote-interface for more information. -### Gitpod - -- Start a Node.js debug configuration from the `Debug` view or hit `F5`. [Detailed instructions](https://medium.com/gitpod/debugging-node-js-applications-in-theia-76c94c76f0a1) - -See https://www.gitpod.io for more information. - ### Eclipse IDE with Eclipse Wild Web Developer extension - From a .js file, choose "Debug As... > Node program", or - Create a Debug Configuration to attach debugger to running Node.js application (already started with `--inspect`). -See https://eclipse.org/eclipseide for more information. +See https://eclipseide.org/ for more information. ## Command-line options From da9c7b9abbc9aa7d02346764bd25efcedced2402 Mon Sep 17 00:00:00 2001 From: Efe Karasakal Date: Tue, 4 Nov 2025 22:31:16 +0100 Subject: [PATCH 3/5] docs(learn): update vscode link --- apps/site/pages/en/learn/getting-started/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/site/pages/en/learn/getting-started/debugging.md b/apps/site/pages/en/learn/getting-started/debugging.md index 5e8ac5ab1b498..796522fd2e55a 100644 --- a/apps/site/pages/en/learn/getting-started/debugging.md +++ b/apps/site/pages/en/learn/getting-started/debugging.md @@ -89,7 +89,7 @@ See [Chrome DevTools Frontend](https://github.com/ChromeDevTools/devtools-fronte - In the Debug panel, click the settings icon to open `.vscode/launch.json`. Select "Node.js" for initial setup. -See https://github.com/microsoft/vscode for more information. +See https://code.visualstudio.com/docs/nodejs/nodejs-debugging for more information. ### Visual Studio 2017+ From fc188a58603bae5a9118b7f71107883dfc1ee422 Mon Sep 17 00:00:00 2001 From: Efe Date: Wed, 5 Nov 2025 17:00:44 +0100 Subject: [PATCH 4/5] Update apps/site/pages/en/learn/getting-started/debugging.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Efe --- apps/site/pages/en/learn/getting-started/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/site/pages/en/learn/getting-started/debugging.md b/apps/site/pages/en/learn/getting-started/debugging.md index 796522fd2e55a..2a95c250406c3 100644 --- a/apps/site/pages/en/learn/getting-started/debugging.md +++ b/apps/site/pages/en/learn/getting-started/debugging.md @@ -80,7 +80,7 @@ Several commercial and open source tools can also connect to the Node.js Inspect #### Option 2: Connect manually - Visit `http://localhost:/json/list`. It should return a JSON object containing a `devtoolsFrontendUrl`. -- Paste the URL directly into your browser's address bar +- Paste the URL directly into your browser's address bar. See [Chrome DevTools Frontend](https://github.com/ChromeDevTools/devtools-frontend) and [Microsoft Edge DevTools Guide](https://learn.microsoft.com/microsoft-edge/devtools-guide-chromium/) for more information. From 204427323710d7976cc18a927375967c33413d68 Mon Sep 17 00:00:00 2001 From: Efe Karasakal Date: Wed, 5 Nov 2025 17:02:41 +0100 Subject: [PATCH 5/5] docs(learn): update debugging docs according to copilot suggestions --- apps/site/pages/en/learn/getting-started/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/site/pages/en/learn/getting-started/debugging.md b/apps/site/pages/en/learn/getting-started/debugging.md index 2a95c250406c3..7e7cc7da59337 100644 --- a/apps/site/pages/en/learn/getting-started/debugging.md +++ b/apps/site/pages/en/learn/getting-started/debugging.md @@ -80,7 +80,7 @@ Several commercial and open source tools can also connect to the Node.js Inspect #### Option 2: Connect manually - Visit `http://localhost:/json/list`. It should return a JSON object containing a `devtoolsFrontendUrl`. -- Paste the URL directly into your browser's address bar. +- Copy the `devtoolsFrontendUrl` value from the response and paste it into your browser's address bar. See [Chrome DevTools Frontend](https://github.com/ChromeDevTools/devtools-frontend) and [Microsoft Edge DevTools Guide](https://learn.microsoft.com/microsoft-edge/devtools-guide-chromium/) for more information.