microsoft / microsoft/vscode-edge-devtools
preLaunchTask is never run when using vscode-edge-devtools.debug
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 828
- Forks
- 359
- Avg merge
- 20h 32m
- Merged PRs (30d)
- 10
Description
Environment (please complete the following information):
- OS (e.g., Windows 10): MacOS 11.6.2
- Extension version (e.g., 1.2.3): 1.4.2
Describe the bug:
When using the vscode-edge-devtools.debug type in a configuration in launch.json, the preLaunchTask is never actually executed, and the Edge debugger opens right away without running anything first. This repros with npm and shell tasks (defined in tasks.json). The behavior is fixed by using pwa-msedge instead.
Repro steps:
- Create a task in
.vscode/tasks.json - Add a
preLaunchTaskproperty into avscode-edge-devtools.debuglaunch configuration in.vscode/launch.jsonreferencing the task label - Run the debug config
Expected behavior:
The specific preLaunchTask should run before the Edge debugger extension. It doesn't.
Additional context:
Related to #501
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with a task in .vscode/tasks.json and a vscode-edge-devtools.debug configuration in .vscode/launch.json, then compare it with the pwa-msedge configuration. Trace how the debug configuration handles preLaunchTask. Done means the referenced npm or shell task runs before the Edge debugger opens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100