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
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,20 +71,25 @@ 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
+
- 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.
81
86
82
87
### Visual Studio Code 1.10+
83
88
84
89
- In the Debug panel, click the settings icon to open `.vscode/launch.json`.
85
90
Select "Node.js" for initial setup.
86
91
87
-
See https://github.com/microsoft/vscode for more information.
92
+
See https://code.visualstudio.com/docs/nodejs/nodejs-debugging for more information.
88
93
89
94
### Visual Studio 2017+
90
95
@@ -104,18 +109,12 @@ See https://github.com/microsoft/vscode for more information.
104
109
105
110
See https://github.com/cyrus-and/chrome-remote-interface for more information.
106
111
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
-
113
112
### Eclipse IDE with Eclipse Wild Web Developer extension
114
113
115
114
- From a .js file, choose "Debug As... > Node program", or
116
115
- Create a Debug Configuration to attach debugger to running Node.js application (already started with `--inspect`).
117
116
118
-
See https://eclipse.org/eclipseide for more information.
0 commit comments