--version argument to include the vsc version

[JtMotoX]

Current:

code-server --version
3.11.1 acb5de66b71a3f8f1cc065df4633ecd3f9788d46

Desired (example):

code-server --version
3.11.1 acb5de66b71a3f8f1cc065df4633ecd3f9788d46 vsc-1.57.1

[jsjoeio]

Neat idea! Thanks for raising. Added to the Backlog Candidates which just means we'll wait for the community to weigh in.

[GirlBossRush]

We technically support this via code-server —version —json

$ code-server --version --json
{
  codeServer: '3.11.1',
  commit: 'b9d79dc1988a30e129aa6452289cc69ad5da7a6c',
  vscode: '1.60.0'
}

[JtMotoX]

We technically support this via code-server —version —json

Oh ok, I didn't realize there was a json flag. Maybe I should have read the documentation. This does not really solve my need though since this is not a valid json response. In the current response, json parsers cannot read it because it is not valid json. Json should have double quotes around the keys and values. Right now there are no double quotes around the keys, and the values have single quotes instead of double.

> code-server --version --json | jq -r '.vscode'
parse error: Invalid numeric literal at line 2, column 13

[GirlBossRush]

@JtMotoX you are absolutely correct, and that’s a very easy fix. We can likely have it out in 3.12.1, however, here’s a temp fix:

$ node -e "console.log(JSON.stringify($(code-server --version --json)))”
{"codeServer":"3.11.1","commit":"acb5de66b71a3f8f1cc065df4633ecd3f9788d46","vscode":"1.57.1"}

[JtMotoX]

This workaround works. I will use this until the changes are applied on your side. Thanks 👍

> node -e "console.log(JSON.stringify($(code-server --version --json)))" | jq -r '.vscode'
1.57.1

> code --version | head -n1
1.57.1

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no activity occurs in the next 5 days.

[jsjoeio]

This was done in #4925 and is included in 4.1.0