Nothing seems to be happening about env-cmd HOT 7 CLOSED

I experience the same issue. can anyone comment if we run it correctly?

"test": "env-cmd ./tests/.env echo $TESTMODE",

from env-cmd.

I'm getting the same result as @amityo

from env-cmd.

Was anyone able to figure out what is wrong? Seeing the same problem.

from env-cmd.

@tomyates @andreialecu I think that I was able to use it properly with something like this:
package.json:

"test:server": "cd dist/tests && env-cmd ../../envs/test.server.env mocha \"{.,!(node_modules)/**}/*.test.js\" 

from env-cmd.

I have added some examples to demonstrate how to use the various options here: https://github.com/toddbluhm/env-cmd-examples

After looking at those, let me know if you are still having issues. If you are on Linux its possible there are still issues. A few others have reported issues on Linux, but it been very sporadic. I have used it on Linux successfully myself. The issues I have seen on Linux tend to be permission issues reading the .env file.

from env-cmd.

It was a problem with the way our project was set up. A babel plugin was embedding process.env.VAR as constants and process.env itself wouldn't contain anything. Was a problem on our end, we verified that this package works properly after all. Sorry, and thank you!

from env-cmd.

Closing due to no additional feedback from other members.

from env-cmd.