Remote Host v1.112.01907 on Loong64 fails to launch due to missing `globalThis.WebSocket`

[CSharperMantle]

Describe the bug

Currently, we bundle Node.js 20.16.0 for Loong64 and RISCV64:

vscodium/build/linux/package_reh.sh

Lines 52 to 63 in cb68d26

	elif [[ "${VSCODE_ARCH}" == "riscv64" ]]; then
	NODE_VERSION="20.16.0"
	VSCODE_REMOTE_DEPENDENCIES_CONTAINER_NAME="vscodium/vscodium-linux-build-agent:focal-devtoolset-riscv64"
	export VSCODE_SKIP_SETUPENV=1
	export VSCODE_NODEJS_SITE='https://unofficial-builds.nodejs.org'
	elif [[ "${VSCODE_ARCH}" == "loong64" ]]; then
	NODE_VERSION="20.16.0"
	VSCODE_REMOTE_DEPENDENCIES_CONTAINER_NAME="vscodium/vscodium-linux-build-agent:beige-devtoolset-loong64"
	export VSCODE_SKIP_SETUPENV=1
	export VSCODE_NODEJS_SITE='https://unofficial-builds.nodejs.org'

microsoft/vscode@383c174#diff-c5f10117e4d60a701184e817193c77b097be82b8708494ebc44153b7c13b4731R209 introduces references to globalThis.WebSocket. However, this API is only available ungated starting from v22.0.0¹. This crashes the extension host and prevents all extensions from loading.

Please confirm that this problem is VSCodium-specific

• This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

• I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

1. Install v1.112.01907.
2. Connect to a Loong64 remote.
3. Observe the crash of extension host in the Output window.

Expected behavior

The Remote Host should launch normally.

Screenshots

2026-03-21 12:00:49.666 [info] Extension host with pid 344570 started
2026-03-21 12:00:49.668 [info] Lock '/home/csmantle/.vscodium-server/data/User/workspaceStorage/bcdf9ce377fff63f6798f60dadefc460/vscode.lock': Lock acquired.
2026-03-21 12:00:49.895 [error] TypeError: Cannot read properties of undefined (reading 'prototype')
    at Module.createWebSocketPatch (/home/csmantle/.vscodium-server/bin/e2b23bbd5646cc28aaa6f26ee53b257c290b6be1/node_modules/@vscode/proxy-agent/out/index.js:729:52)
    at Tte (file:///home/csmantle/.vscodium-server/bin/e2b23bbd5646cc28aaa6f26ee53b257c290b6be1/out/vs/workbench/api/node/extensionHostProcess.js:244:24110)
    at Ite (file:///home/csmantle/.vscodium-server/bin/e2b23bbd5646cc28aaa6f26ee53b257c290b6be1/out/vs/workbench/api/node/extensionHostProcess.js:244:22764)
    at mie._beforeAlmostReadyToRunExtensions (file:///home/csmantle/.vscodium-server/bin/e2b23bbd5646cc28aaa6f26ee53b257c290b6be1/out/vs/workbench/api/node/extensionHostProcess.js:283:1002)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async mie.initialize (file:///home/csmantle/.vscodium-server/bin/e2b23bbd5646cc28aaa6f26ee53b257c290b6be1/out/vs/workbench/api/node/extensionHostProcess.js:120:11716)

$ ~/.vscodium-server/bin/e2b23bbd5646cc28aaa6f26ee53b257c290b6be1/node --version
v20.16.0
$ ~/.vscodium-server/bin/e2b23bbd5646cc28aaa6f26ee53b257c290b6be1/node
Welcome to Node.js v20.16.0.
Type ".help" for more information.
> WebSocket
Uncaught ReferenceError: WebSocket is not defined

Desktop (please complete the following information):

Version: 1.112.01907 (system setup)
Commit: e2b23bbd5646cc28aaa6f26ee53b257c290b6be1
Date: 2026-03-17T18:09:23Z
Electron: 39.8.0
ElectronBuildId: undefined
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26220

Additional context

N/A.

Footnotes

1. https://nodejs.org/docs/v24.14.0/api/globals.html#class-websocket ↩

[CSharperMantle]

Symlinking the shipped node executable to a Node.js v22 binary fixes the problem.