microsoft / microsoft/node-jsonc-parser
Add dev container
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- TypeScript
- Stars
- 759
- Forks
- 66
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 7
Description
I have a general preference for working with VS Code dev containers to keep tools and dependencies isolated between projects. Would you be open to a PR contributing a dev container?
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 target files, tests, or entry points are named. Review the repository's existing TypeScript tooling and determine the intended VS Code dev-container setup; done means a complete, usable configuration is added and documented for contributors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100