Does env-cmd support this? How? about env-cmd HOT 2 CLOSED

@Pronan I think you mis-understand how webpack works. Webpack compiles existing js files into just one js file, so webpack needs to know what vars to replace. The above env vars you provided are sent to webpack, you have to tell webpack (via webpack.config.js) to replace those vars in your js files with the ones in the config.env file.

Look at https://webpack.js.org/plugins/define-plugin/ for more info. You will end up with something like this in your webpack config:

plugins: [
  new webpack.DefinePlugin({
    "ENV.FOO": process.env.foo,  // process.env is a special nodejs object that holds all env vars
    "ENV.BAR": process.env.bar
  }),
]

Edit:

It looks like webpack has a new environment variable plugin that makes this process even easier and allows for node style env vars (process.env.FOO). Using EnvironmentPlugin (https://webpack.js.org/plugins/environment-plugin/) your code and files would look like this:

index.js

var x = [process.env.FOO, process.env.BAR]

webpack.config.js

plugins: [
  new webpack.EnvironmentPlugin(['FOO', 'BAR'])
]

from env-cmd.

I'll check that. Thank you!

from env-cmd.