How is cross-env different from dotenv ? about cross-env HOT 5 CLOSED

Nope, you're fine. This was an ok place to ask the question.

from cross-env.

cross-env is a CLI that will spawn a process for the command you give it with the environment variables set as you specify in the command.

dotenv will spawn the process with the environment variables based on a .env file.

Both are useful. Depends on your needs.

from cross-env.

@kentcdodds why doesn't cross-env allow to source .env file and use it instead of dotenv module?

from cross-env.

So you're saying that cross-env is literally the same thing from native Webpack's environment variables - as it is in their documentation?

webpack --env.PORT=3000 --env.ENV=development --config webpack.common.js for example, the difference is being in module.exports you don't set it to an object, but to a function which receives an environment object, and you can extract data from there and do logic where necessary:

module.exports = env => {
  // Use env.<YOUR VARIABLE> here:

from cross-env.

This project was created years ago. Long before the --env flag existed for webpack. So maybe the examples in the README are dated. But there are still plenty of situations where you'd want to run a script with environment variables set.

from cross-env.