Repository navigation
Bump vscode to 1.101.0 (Node 22 / Electron 35) #1850
Description
Activity
One reason for me is that I have some old production systems running Ubuntu 16.04/18.04 which is no longer supported by latest vscode remote ssh. The last version that supports these legacy systems is vscode 1.98.2.
One reason for me is that I have some old production systems running Ubuntu 16.04/18.04 which is no longer supported by latest vscode remote ssh. The last version that supports these legacy systems is vscode 1.98.2.
@eitsupi could you say a little more about what updating to Node >= 22 brings us? Unless there is some important functionality that we're missing out on, I'd prefer to remain conservative and retain the current support.
There is a concrete reason I was considering Node 22 for 3.2.0: I want to remove the abandoned httpgd JS client and replace it with a small built-in client.
Node 22 gives us a stable built-inWebSocket, which would let us drop the oldhttpgd/ws/
isomorphic-ws/cross-fetchdependency chain.That said, I understand the legacy Ubuntu / VS Code 1.98.2 concern.
I think a reasonable compromise is to keep the current VS Code minimum for 3.2.0, use nativeWebSocketwhere available, and fall back to httpgd's HTTP polling API on older extension hosts.Node 20 is already EOL, so I don't think it should remain our long-term baseline.
Makes sense, 1.98.2 could still use an older version of vscode-R, which I think is sufficient for me.
- added a commit that references this issue
on Oct 9, 2026
There seems to be no reason to stay on Node 20.