You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/site/pages/en/learn/getting-started/debugging.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,13 +71,18 @@ Several commercial and open source tools can also connect to the Node.js Inspect
71
71
72
72
### Chrome DevTools 55+, Microsoft Edge
73
73
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
79
75
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
+
- Paste the URL directly 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.
0 commit comments