feat(code-server): install extensions from .vscode/extensions.json

[michaelbrewer]

Add a new flag auto_install_extensions which auto installed the recommended extensions found in .vscode/extensions.json

Example .vscode/extensions.json

{
    "recommendations": [
        "hashicorp.terraform"
    ]
}

Example terraform template snippet

module "code-server" {
 source                   = "registry.coder.com/modules/code-server/coder"
  version                 = "1.0.13"
  agent_id                = coder_agent.main.id
  folder                  = "/home/${local.username}/modules"
  install_prefix          = "/home/${local.username}/.code-server"
  extensions_dir          = "/home/${local.username}/.code-server/extensions"
  use_cached              = true
  auto_install_extensions = true
}

Example output

NOTES

• This does require jq to be installed on the workspace
• This will look in the $HOME directory for .vscode/extensions.json if folder is not set
• For performance of restarts (using use_cached and extensions_dir together helps)

closes #206

[code-asher]

Neat!

[code-asher]

Not sure if this is overkill, but we could use the Node bundled with code-server.

extensions=$("$INSTALL_PREFIX/lib/node" -e "require(\"$WORKSPACE_DIR/.vscode/extensions.json\").recommendations.forEach((r) => console.log(r))")

[michaelbrewer]

Interesting. I do like jq, but if we know the path to node and it should always be present, then it makes sense.

[michaelbrewer]

@code-asher i am not 100% convinced about the flag auto_install_extensions, if it makes sense i will keep it,

I will back port these features to the vscode-web module to people can easily switch between the 2 versions.

[code-asher]

i am not 100% convinced about the flag auto_install_extensions, if it makes sense i will keep it,

I think code-server/VS Code already offers to install the recommended extensions after you open a project, right? But this can cut down on the perceived time it takes to get coding, so I feel it is a worthwhile addition.

[michaelbrewer]

More of the naming of the flag.

I like the intention of this, as it allows for the get repo to specify what it wants.

[code-asher]

More of the naming of the flag.

Ohh yeah I see, I think the name is good.