Pass private environment variables as arguments to npm scripts

Basically, this example pretty much sums up what I want to do.

Although, I’ll provide you with my use-case.

I have a secret key called API_KEY that I want to access inside of package.json’s scripts.

package.json

{
   "scripts": {
      "start": "web-ext run --api-key=API_KEY"
   }
}

My .env file contains API_KEY which I want to keep private:

API_KEY=abc123

Now if I use cmd-env, I can’t pass it as an argument to --api-key

I want the following to work 👇

{
   "scripts": {
      "start": "cmd-env web-ext run --api-key=$API_KEY"
   }
}

Any way to add that?

[toddbluhm]

Hey sorry for taking so long to reply to this.

The original goal was for the --use-shell option to be able to enable the functionality of replacing $VAR similar to how cross-env does it here: https://github.com/kentcdodds/cross-env#cross-env-vs-cross-env-shell. Unfortunately, that does not seem to work as expected.

I tried a couple of different ways to make it work, but no dice. I think what I am going to have to do is implement some sort of parsing of the full shell command before execution and manually replace $VAR and ${VAR} and %VAR% (windows) with the final env value. Not sure how well this will work, but it is a start.

[toddbluhm]

@omeid interesting idea, but I do not use cross-env in the package and I would rather not add an additional dependency, unless absolutely necessary. I liked your PR so I merged that one.