Consider official Deno devcontainer feature

[jcbhmr]

Hello! 👋

I'm interested in seeing if this @denoland organization would be willing to consider a denoland/devcontainer-features repository to house an official Deno devcontainer feature for GitHub Codespaces (and other devcontainer environments).

Example:

// .devcontainer/devcontainer.json
{
  "features": {
    "ghcr.io/denoland/devcontainer-features/deno": {}
  }
}

In the current official devcontainers/features repository, they are not accepting new features and are instead encouraging users to make their own. I think it would be beneficial to follow in the footsteps of other organizations like Julia, R, Mamba, and others by creating and maintaining an official Deno installer feature.

Deno already has its own denoland/setup-deno GitHub Action that is under the official umbrella, and I think having a similar repository for devcontainer features would be helpful for the community.

If this isn't tenable, that's OK! 👍 It's possible (and even probable) that there will be some kind of @devcontainers-community features repository that could house community-driven features. It'd just be nice if it were under the official umbrella.

Stemmed from devcontainers-community#1

[mwmcode]

👍

The development containers docs seem outdated?

• Remote-Containers Dev. Containers: Add Development Container Configuration File
• The only Deno options available are ones by rsm-hcd (not official).

We can either follow @jcbhmr's suggestions or at least update the docs with steps on how to do it manually using the official Deno docker images. Example: creating Deno Vite-React app in a development container:

.devcontainer/devcontainer.json

{
  "name": "Deno",
  "image": "denoland/deno",
  "customizations": {
    "vscode": {
      "settings": {},
      "extensions": ["denoland.vscode-deno"]
    }
  },
  "postCreateCommand": "deno install"
}