fixed this by changing line 26 of
~/.local/share/code-server/extensions/wraith13.unsaved-files-vscode-2.0.0/out/src/extension.js
// const localeTableKey = JSON.parse(process.env.VSCODE_NLS_CONFIG).locale;
const localeTableKey = "en-us";

Can we get a VSCODE_NLS_CONFIG in code-server? there are a few extensions that use it.
Also, in chrome devtools opened on code-server window I don't see "process.env" (or process for that matter) but in devtools for regular vscode I do see it.

@jots process is a Node.js API. We don't want that lurking in code-server's side.

CC @multishifties

So, @foresthoffman would normally have been the guy to talk to for anything extension related. Microsoft TOS doesn't allow us to use their marketplace directly.

I see no reason why we can't add a VSCODE_NLS_CONFIG env variable. @jots Can you change this issue to something like:

VSCODE_NLS_CONFIG returns undefined, No process variable for VSCODE_NLS_CONFIG, or VSCODE_NLS_CONFIG causing extension install failure?