Is processing commands arguments as its own about dotenv-cli HOT 3 CLOSED

please read the readme before filing isues https://github.com/entropitor/dotenv-cli#flags-to-the-underlying-command

from dotenv-cli.

I saw that but I think I got confused because the example is backwards

This is what is there now:

E.g. the following command without dotenv-cli:
$ mvn exec:java -Dexec.args="-g -f"
will become the following command with dotenv-cli:
$ dotenv -- mvn exec:java -Dexec.args="-g -f"

It should be written:

$ dotenv -- mvn exec:java -Dexec.args="-g -f"
will become the command to dotenv-cli
$ mvn exec:java -Dexec.args="-g -f"

Also: this way of parsing command line arguments unfortunately doesn't work well with npm scripts, like dotenv and godotenv do.

in package.json
"test": "node -r dotenv/config node_modules/.bin/ava",
$ npm run test -- -wv
runs
node -r dotenv/config node_modules/.bin/ava "-wv"

in package.json
"testwithgodotenv": "godotenv ava",
npm run testwithgodotenv -- -wv
runs
godotenv ava "-wv"

in package.json
"testwithdotenv": "dotenv ava",
$ npm run testwithdotenv -- -wv
runs
dotenv ava "-wv" <--- the original error in the issue

from dotenv-cli.

1. The readme says how to construct the dotenv command. I think this is what is most useful to people getting started. Feel free to create a PR to improve it but keep in mind that it should explain how to use it, not how it works
2. Given it's such a common idiom to ignore everything after --, npm and others also use it so what you want is

npm run testwithdotenv -- -- -wv

Notice the double --, one to say, npm don't parse anything after these but pass them along and another to say to dotenv-cli do not parse anything after these...

So dotenv sees dotenv ava -- "-wv" and ava sees ava "-wv"

from dotenv-cli.