Skip to content

Commit ffb08c7

Browse files
committed
Clarify
1 parent b649410 commit ffb08c7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/debugging.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Debug your Next.js app.
44

55
# Debugging
66

7-
This documentation explains how you can debug your Next.js frontend and backend code with full source maps support using either the [Chrome DevTools](https://developers.google.com/web/tools/chrome-devtools) or the [VSCode debug panel](https://code.visualstudio.com/docs/editor/debugging).
7+
This documentation explains how you can debug your Next.js frontend and backend code with full source maps support using either the [Chrome DevTools](https://developers.google.com/web/tools/chrome-devtools) or the [VSCode debugger](https://code.visualstudio.com/docs/editor/debugging).
88

99
It requires you to first launch your Next.js application in debug mode in one terminal and then connect an inspector (Chrome DevTools or VS Code) to it.
1010

@@ -63,7 +63,7 @@ Create a file named `.vscode/launch.json` at the root of your project with this
6363
}
6464
```
6565

66-
Now hit <kdb>F5</kbd> or go to the VS Code debug panel and click on "Launch program" (which just attaches VS Code to the running debugger) and you can start your debugging session.
66+
Now hit <kdb>F5</kbd> or select **Debug: Start Debugging** from the Command Palette and you can start your debugging session.
6767

6868
## Step 3: Put breakpoints and see what happens
6969

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy