microsoft / microsoft/vscode-js-debug
Please address issues in vscode-js-debug-browsers repo
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 373
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 6
Description
Maintainers, if you could take a look at issues in the vscode-js-debug-browsers repo it will be great. These issues have no progress for most of the past year. Since issues in this repo are assigned promptly, I think maybe you simply missed the ones over there. Thanks!
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
Open the linked vscode-js-debug-browsers issue tracker and identify a specific unaddressed issue; this report names no file, test, or entry point. Done cannot be defined from this issue alone, so a contributor needs a selected issue and maintainer confirmation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100