如何在 package.json 内的 npm 脚本中使用 SECRET_ENV？

Question

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 :

API_KEY=abc123

How can I access the value of API_KEY inside package.json 's scripts while still keeping it a secret because I need to push package.json publicly?

Currently, I do the following which works but not cross-platform:

package.json

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

And when running start script I do it like:

API_KEY=abc123 npm start

This works thanks to Bash Programming Language but it doesn't work on Windows. I need to replace $API_KEY in start script with %API_KEY% . But I want it to be cross-platform. Is there any other way?

Answer 1

The only other viable answer to this I found so far is a bit hacky:

{
   "scripts": {
      "start": "web-ext run --api-key=$(grep API_KEY .env | cut -d '=' -f2)"
   }
}

[ https://stackoverflow.com/a/58038814/1822977 ]

Answer 2

You can simply require "dotenv" lib, and access var from process.env.{SOME_KEY}

Answer 3

For cross platform

1) You can use 'npm env-cmd ' as a devDependencies .

Setting the environment from a file

Usage

Environment file ./.env

# This is a comment
API_KEY=abc123

Package.json

{
  "scripts": {
    "start": "env-cmd web-ext run"
  }
}

---

2) You can use 'npm cross-env ' as a devDependencies .

Run scripts that set and use environment variables across platforms

Usage

{
  "scripts": {
    "start": "cross-env API_KEY=abc123 web-ext run"
  }
}

---

For Windows only

You can try something like this:

cmd /C "set API_KEY=abc123 && npm start"

As Viper_Sb says here :

/C exits the new cmd right away after running, if you produce output with the new one it will still be visible in the parent window.

You can opt to use /K in which case the new cmd window stays open at the end of the run.