Skip to content

Commit e2b6839

Browse files
efekrsklCopilot
andauthored
docs(learn): improve debugging docs (#8329)
* docs(learn): improve debugging docs * docs(learn): remove gitpod section * docs(learn): update vscode link * Update apps/site/pages/en/learn/getting-started/debugging.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Efe <dogukankrskl@gmail.com> * docs(learn): update debugging docs according to copilot suggestions --------- Signed-off-by: Efe <dogukankrskl@gmail.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent e0c6c49 commit e2b6839

File tree

1 file changed

+13
-14
lines changed

1 file changed

+13
-14
lines changed

apps/site/pages/en/learn/getting-started/debugging.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -71,20 +71,25 @@ Several commercial and open source tools can also connect to the Node.js Inspect
7171

7272
### Chrome DevTools 55+, Microsoft Edge
7373

74-
- **Option 1**: Open `chrome://inspect` in a Chromium-based
75-
browser or `edge://inspect` in Edge. Click the Configure button and ensure your target host and port
76-
are listed.
77-
- **Option 2**: Copy the `devtoolsFrontendUrl` from the output of `/json/list`
78-
(see above) or the --inspect hint text and paste into Chrome.
74+
#### Option 1: Use the built-in DevTools UI
7975

80-
See https://github.com/ChromeDevTools/devtools-frontend, https://www.microsoftedgeinsider.com for more information.
76+
- Open `chrome://inspect` (`edge://inspect` in Microsoft Edge) in your browser.
77+
- Click the Configure button and ensure your target host and port are listed.
78+
- Your Node.js application should appear in the Remote Target list.
79+
80+
#### Option 2: Connect manually
81+
82+
- Visit `http://localhost:<inspect-port>/json/list`. It should return a JSON object containing a `devtoolsFrontendUrl`.
83+
- Copy the `devtoolsFrontendUrl` value from the response and paste it into your browser's address bar.
84+
85+
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.
8186

8287
### Visual Studio Code 1.10+
8388

8489
- In the Debug panel, click the settings icon to open `.vscode/launch.json`.
8590
Select "Node.js" for initial setup.
8691

87-
See https://github.com/microsoft/vscode for more information.
92+
See https://code.visualstudio.com/docs/nodejs/nodejs-debugging for more information.
8893

8994
### Visual Studio 2017+
9095

@@ -104,18 +109,12 @@ See https://github.com/microsoft/vscode for more information.
104109

105110
See https://github.com/cyrus-and/chrome-remote-interface for more information.
106111

107-
### Gitpod
108-
109-
- 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)
110-
111-
See https://www.gitpod.io for more information.
112-
113112
### Eclipse IDE with Eclipse Wild Web Developer extension
114113

115114
- From a .js file, choose "Debug As... > Node program", or
116115
- Create a Debug Configuration to attach debugger to running Node.js application (already started with `--inspect`).
117116

118-
See https://eclipse.org/eclipseide for more information.
117+
See https://eclipseide.org/ for more information.
119118

120119
## Command-line options
121120

0 commit comments

Comments
 (0)