Created
August 4, 2021 18:30
-
-
Save AlphaT7/0fee9abbfbfc3082ae27464a8b7a06b7 to your computer and use it in GitHub Desktop.
VS-Code-Debugging Setup
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // launch.json | |
| { | |
| "version": "0.2.0", | |
| "configurations": [ | |
| { | |
| "type": "pwa-chrome", | |
| "request": "attach", | |
| "name": "Attach to Chrome", | |
| "port": 9222, | |
| "urlFilter": "http://localhost:8080/*", | |
| "webRoot": "${workspaceFolder}", | |
| "outputCapture": "std", | |
| } | |
| ] | |
| } | |
| # Launch chrome with the following parameter: --remote-debugging-port=9222 | |
| # Make sure that the port in this parameter is the same as the one configured in 'port' property of the attach to chrome configuration in the launch.json file (like the example above) | |
| # You can add this parameter in your chrome shortcut properties by: | |
| # Right click your shortcut file and select properties | |
| # Chain it to Target property, e.g. | |
| # "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 | |
| # Link: https://newbedev.com/cannot-debug-in-vs-code-by-attaching-to-chrome |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment