Asher

Closing since this does not appear to be a code-server bug, but please feel free to continue commenting if you need help.

This is a great idea, but I think this would be too much of a rework to be maintainable as a patch here in code-server. I think keeping the extension...

Looks like a duplicate of https://github.com/coder/code-server/issues/5561? I am not sure what the fix is.

Could you test this in Codespaces as well? Seems like the sort of thing that could be an upstream bug.

The logs say the web socket failed to connect. Is your proxy not set up to proxy web sockets?

Thank you for the PR! This project just wraps the version used in VS Code, since that is the one that is tested and supported by them: https://github.com/microsoft/vscode/blob/main/remote/.yarnrc Once they...

Oh weird I wonder why they chose to do that. Oh it probably matches whatever Node version is being used in Electron...

Does this happen in Codespaces? It sounds more likely to be a bug with VS Code than with code-server, at first glance, but not impossible.

Probably related: https://github.com/coder/code-server/issues/5561 https://github.com/coder/code-server/issues/5430 Does the `npm i argon2` command have any errors? Does `npm rebuild` help? I think we should try moving away from `argon2`.

Yeah I am not sure, it seems like either a bug in argon2 or npm. Although, the prompt says you are in `~`; is that the right directory? I would...