.env file does not have an app associated about env-cmd

[toddbluhm]

So quick update on this. I just noticed that in the command cross-env NODE_ENV=development env-cmd .env node server it is missing the -f flag. Starting with env-cmd@v9 and later, in order to pass a custom env file location you have to use the -f flag.

The command should be:
cross-env NODE_ENV=development env-cmd -f .env node server

If the .env file is located in the project root and named .env then you do not need to pass anything:
cross-env NODE_ENV=development env-cmd node server

Let me know how that works. I have my windows side up and running. I also just added windows support to the env-cmd examples repo here: https://github.com/toddbluhm/env-cmd-examples with all tests passing.

[toddbluhm]

That is odd. Are you using the same version of cross-env when executing it using env-cmd@8?

Honestly, I really just need to spin up my windows side and spend some time testing env-cmd there to see how things perform and fix all the weird bugs that show up.

[alekslario]

bump

same issue here

[toddbluhm]

Another quick update. I just finished adding a test runner for windows on this repo as well. You can see the windows test status badge on the readme page. So now both env-cmd and env-cmd-examples repos have full windows support in test runners. Let me know if your still having issues on windows and please include some specifics 😄

[toddbluhm]

Closing due to inactivity