devcontainers-community / devcontainers-community/features-deno
Reach out to original authors
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Hello! 👋👋
@nmemoto https://github.com/nmemoto/devcontainer-features/tree/main/src/deno
@progamesigner https://github.com/progamesigner/devcontainers/tree/master/features/deno
I noticed that you have devcontainer features for Deno and I thought you might be interested in this project.
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
No repository file, test, or entry point is identified. Start by reviewing the linked Deno feature implementations and the current project context; the work is only defined once the original authors respond or a concrete follow-up scope is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100