Add dev container

Open
#45 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript, vscode
Domain
developer-experience, tooling

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.

Description

feature-request

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?

Dominant language
TypeScript
Stars
759
Forks
66
Avg merge
5d 10h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

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.

More from microsoft/node-jsonc-parser

All issues in microsoft/node-jsonc-parser

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.