Export the variables if no command is given about dotenv-cli HOT 3 CLOSED

@RamIdeas this is simply not possible because it's not dotenv-cli who evaluates too early but your shell before even passing this value to dotenv-cli, see also #31 (comment) for more information

what you can do is have 2 scripts

// package.json
{
  "scripts": {
    "echo:raw": "echo $VAR_NAME",
    "echo": "dotenv -- yarn echo:raw",
  }
}

from dotenv-cli.

I feel like I didn't explain myself clearly enough. I'm aware it's the shell that evaluates early.

My recommendation is to export the vars if no command is given. Notice the semicolon in the example on the last line?

from dotenv-cli.

Ah okay, that makes more sense.

However, I don't think dotenv can change the env values of the outer shell script, that seems like it would be dangerous security wise?

$ URL=example.com
$ bash -c 'echo $URL' # doesn't output google.com because wasn't exported
$ export URL=example.com
$ bash -c 'echo $URL' # does output goolge.com because it was exported
$ bash -c 'export URL=google.com'
$ echo $URL      # doesn't have google.com because child doesn't export to parent

I'd be happy to implement something if you can prove me wrong. I'd probably put it behind a feature flag then but for the rest it should be fine. I'm just not sure if it can be done.

from dotenv-cli.