= and all following contents discarded from .env environment variables

[DanielRosenwasser]

It appears that the contents of variables loaded from .env (or envFile) are incorrectly set if they contain an = within the value.

To repro this, add the following .env file to the top level of a workspace.

OOPS="WHAT=THE"
SOME_ENV_VARIABLE=https://example.com?api-version=2024-02-15-preview

Then create a new terminal and run the following commands

echo $OOPS
echo $SOME_ENV_VARIABLE

Current Behavior

WHAT
https://example.com?api-version

Expected Behavior

WHAT=THE
https://example.com?api-version=2024-02-15-preview

[DanielRosenwasser]

Compounded with the behavior of dotenv described at #22982, this causes all sorts of unexpected behavior. I couldn't tell where my environment variables were being set within a Codespace and was banging my head against this before I opened up microsoft/TypeChat#211.

[karrtikr]

This is actually an issue on VS Code: microsoft/vscode#197603, closing as duplicate. We encourage you interact with that issue to raise priority.

[DanielRosenwasser]

With microsoft/vscode#207889, this will be fixed in the March 2024 release of VS Code.

[karrtikr]

Thanks!