"Intl.DateTimeFormat().resolvedOptions().locale" returns different values in extension host to VS Code process

[DanTup]

I'm using MacBook with its system language set to en-GB. I launched VS Code (from the dock, not the terminal) and if I run:

Intl.DateTimeFormat().resolvedOptions().locale

in the Chrome dev tools console, I see this:

However, in an extension's activate function if I do this:

console.log(Intl.DateTimeFormat().resolvedOptions().locale);

Then I see this:

I need to get the system language in order to set the LANG env variable for spawned processes because CocoaPods crashes if LANG is not set to something-UTF-8, and there's no way to set it without a language part so I need to get at the system language.

[alexdima]

I don't think we have any code to reset/remove things. @deepak1556 Do you have any ideas? (the extension host is using ELECTRON_RUN_AS_NODE)

[DanTup]

FWIW we've worked around this in Flutter. It still seems weird these don't line up and it might be useful for the extension host to have access to it, but it's not pressing for me anymore. Thanks!

[deepak1556]

I can confirm this issue,

@alexandrudima here are my observations.

1. Renderer process prints the proper locale
2. Extension host reports incorrect locale
3. Running the Code executable from command line with export ELECTRON_RUN_AS_NODE=1 set code -e 'console.log(Intl.DateTimeFormat().resolvedOptions().locale)' prints the correct locale.

To make things more concrete, v8 and icu are shared between node and electron so behavior being different between these two processes are highly unlikely unless we are intervening.

[deepak1556]

Okay I have narrowed down the issue, it seems to be a problem with child_process module that is messing with the locale. Tried the following sample

const { spawn } = require('child_process');
const locale = spawn("/Users/demohan/Downloads/electron-v6.1.5-darwin-x64/Electron.app/Contents/MacOS/Electron", ['-e', 'console.log(Intl.DateTimeFormat().resolvedOptions().locale)'], {env: {
	'ELECTRON_RUN_AS_NODE': 1
}});

locale.stdout.on('data', (data : any) => {
  console.log(`stdout: ${data}`);
});

locale.stderr.on('data', (data : any) => {
  console.error(`stderr: ${data}`);
});

prints en-US while running on the command line prints the proper system locale used at the moment, in my case de