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
{{ message }}
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
Log file (set "trace": true in launch config): Checked 'C:\Users\cpayne\AppData\Local\Temp', but no log file was present (was looking for the file 'vscode-edge-debug2.txt'
Steps to reproduce:
Disabled all installed debuggers in VS Code
Enabled Debugger for Microsoft Edge, v1.0.15
Closed and reloaded VS Code as administrator.
Installed latest of 'react-app-polyfill', and ran 'npm run build' on my React app to ensure everything compiles.
I added the launch configuration, ran the 'start msedge' command, attached Edge to VS Code, then ran 'yarn start'.
Expected Behavior:
Running 'yarn start' serves the React app and opens a tab/window in Microsoft Edge. Once the app is running, I can attach my debugger to the running application and debug.
Actual Behavior:
VS Code serves the app, but launces a tab in Chrome. There is nothing in my launch.json file regarding launching or attaching a process to anything except MS Edge. If I try to navigate to the port where Edge is supposed to be listening (http://localhost:8080), I just get a 'ERR_CONNECTION_REFUSED' error message.