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: src/Microsoft.AspNetCore.SpaServices/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -729,7 +729,7 @@ You have two options to get breakpoints that will be hit as expected:
729
729
If you're using Visual Studio Code and Chrome, you can set breakpoints directly on your TypeScript source code in the IDE. To do this:
730
730
731
731
1. Install VS Code's [*Debugger for Chrome* extension](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome)
732
-
2. Ensure your application server has started and can be reached on `localhost` (for example, run `dotnet watch run`)
732
+
2. Ensure your application server has started and can be reached with a browser (for example, run `dotnet watch run`)
733
733
3. In VS Code, open its *Debug* view (on Windows/Linux, press `ctrl`+`shift`+`d`; on Mac, press `cmd`+`shift`+`d`).
734
734
4. Press the cog icon and when prompted to *Select environment*, choose `Chrome`. VS Code will create a `launch.json` file for you. This describes how the debugger and browser should be launched.
735
735
5. Edit your new `.vscode/launch.json` file to specify the correct `url` and `webRoot` for your application. If you're using the project templates in this repo, then the values you probably want are:
@@ -741,7 +741,7 @@ If you're using Visual Studio Code and Chrome, you can set breakpoints directly
741
741
6. Start the debugger:
742
742
* While still on the *Debug* view, from the dropdown near the top-left, choose "*Launch Chrome against localhost, with sourcemaps*".
743
743
* Press the *Play* icon. Your application will launch in Chrome.
744
-
* If you get the error *Cannot connect to runtime process*, that's because you already have an instance of Chrome running. Close it first, then try again.
744
+
* If it does nothing for a while, then eventually gives the error *Cannot connect to runtime process*, that's because you already have an instance of Chrome running. Close it first, then try again.
745
745
7. Finally, you can now set and hit breakpoints in your TypeScript code in VS Code.
746
746
747
747
For more information about VS Code's built-in debugging facilities, [see its documentation](https://code.visualstudio.com/Docs/editor/debugging).
0 commit comments