microsoft / microsoft/vscode-js-debug-companion
Allow installing on vscode.dev
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 17
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
Description
When I tried to get vscode-js-debug to attach to a remote instance of Chrome, it throws this error Error launching browser: command 'js-debug-companion.launchAndAttach' not found
I traced it and found that it was because vscode-js-debug-companion does not allow itself to be installed in codespaces.
Can we allow this to be installable on codespaces?
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Start by locating the extension manifest and its Codespaces or web installation restrictions, then verify that the companion can be installed in vscode.dev and Codespaces and that js-debug-companion.launchAndAttach is available for remote Chrome attachment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100