3 ms·
The way most people learned this is because somewhere in the middle of last year, VSCode's node install stopped working with the old glibc. https://github.com/
by gopalv 2y ago
The way most people learned this is because somewhere in the middle of last year, VSCode's node install stopped working with the old glibc.
https://github.com/microsoft/vscode/issues/201129 https://github.com/microsoft/vscode/issues/201129
Most people who hit this hard pinned their vscode to 1.85 & it took a while till this turned into a simple nag bar on top of their editor.
- nooorofe 2y agoit was fixed with workaround, in newer versions, they copy statically compiled nodejs to the server and it works.