Not able to inject environment variables

[sahibjotsaggu]

Couldn't find anything in the documentation but after learning that something like

execa`MY_ENV=testing echo $MY_ENV`

won't work, I saw that we can use the Options argument to define environment variables.

However, trying the following did not work as expected:

const { stdout } = await execa({
  extendEnv: true,
  env: {
    $MY_ENV: "test",
  },
})`echo $MY_ENV`;
console.log(stdout); // $MY_ENV instead of test

Here's the sandbox

[ehmicky]

Hi @sahibjotsaggu,

Thanks for reaching out. The answer to your question is in #1081 (and in the documentation links mentioned in that issue).

As a side note, please note that the environment variable names in the env option should not start with $. I.e. you want to do env: {MY_ENV: "test"}, not env: {$MY_ENV: "test"}.

[sahibjotsaggu]

Okay, I see from https://github.com/sindresorhus/execa/blob/main/docs/bash.md#environment-variables that environment variables should get injected but I'm getting this type error I can't seem to resolve:

No overload matches this call.
  The last overload gave the following error.
    Object literal may only specify known properties, and 'env' does not exist in type 'URL'.ts(2769)
script.d.ts(22, 2): The last overload is declared here.

Any insight into this?

[ehmicky]

Hi @sahibjotsaggu,

To help solving those issues, I would recommend:

• Creating different issues since this is different from the initial problem
• Pasting the code instead of a screenshot, so we can copy-paste it
• For type-related problems, including a fully reproducing example with https://www.typescriptlang.org/play
• Include environment information: Node.js version, TypeScript version, TypeScript config

I have created the following reproduction, and your example works fine for me.

Is there anything in the TypeScript documentation's troubleshooting section that's helping? In particular: the part about the minimum TypeScript version, and the part about ES modules.