microsoft / microsoft/vscode-edge-devtools

edge error on launch

Open
#3,681 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
827
Forks
358
Avg merge
20h 32m
Merged PRs (30d)
10

Description

Environment (please complete the following information):

  • OS (e.g., Windows 10):
  • Extension version (e.g., 1.2.3):
v2.1.9

Describe the bug:

"Cannot launch a project without a valid launch.json. Please open a folder in the editor.", "Error while fetching list of available targets No available targets to attach."
"Error running command vscode-edge-devtools-view.launch: Failed to launch the browser process!

TROUBLESHOOTING: https://pptr.dev/troubleshooting
. This is likely caused by the extension that contributes vscode-edge-devtools-view.launch."
Image

after trying auto configure and setting my url to my project. i try to launch project and i get failed to launch edge error then asks me if i want to do auto config again.. i then modified config manually from pwa-msedge to jus msedge and this time it semi launched but with a message asking to debug. so i selected debug but nothing appeared in debug console about anything. then finally a edge tab appeared in my workspace but it was an empty blank headless page. which thankfully loads to my main project url but only displays the dev tools now of my project page. no way to view webpage...

Expected behavior:

similar to simple browser a dev web browser would appear within a tab on the workspace in vscode. and i could interreact and debug my project directly in vscode, and do not need to access through a seperate browser. also expect to not get any errors.

Additional context:

Image Image Image Image Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure from the vscode-edge-devtools-view.launch command using the reported launch.json, pwa-msedge, and msedge configurations. Check the linked Puppeteer troubleshooting guidance and the missing OS details; done means Edge launches without errors and the project webpage, rather than only a blank headless DevTools tab, is visible.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.