Environment variables set on webpack.config.client.development.js are not respected.

[JoseInTheArena]

When I set an environment variable as in here: the values do not make it through. For example, if I add a new entry and then console.log it, I get undefined

[catamphetamine]

Provide an exact use case

[JoseInTheArena]

I want to add a new env variable that has different values for production and development. I did so by adding it on the link I posted above and it's undefined. The env variable is for configuring an exception logging library.

[catamphetamine]

Post the exact code

[JoseInTheArena]

On webpack.config.client.development.js I add SENTRY_DSN to process.env. Then I go to client/rendering-service/main.js and client/src/components/Menu.js and add console.log(process.env.SENTRY_DSN).

webpack.config.client.development.js

  // environment variables
  new webpack.DefinePlugin({
    process.env: {
      NODE_ENV: JSON.stringify('development'),
      BABEL_ENV: JSON.stringify('development/client'), 
      SENTRY_DSN: JSON.stringify('some value)
    },
    REDUX_DEVTOOLS : false  // enable/disable redux-devtools
  }),
);

client/rendering-service/main.js and client/src/components/Menu.js

console.log("SENTRY_DSN: ");
console.log(process.env.SENTRY_DSN);

Output on the terminal after running npm run dev

SENTRY_DSN: 
undefined

[catamphetamine]

Webpack variables aren't available in main.js

[JoseInTheArena]

That's interesting. If I add the variable in webpack.config.js instead, it is available. I'll keep looking. Thanks for the help.

[catamphetamine]

No, it can not be available in main.js because it's unrelated to Webpack.
It is available only in Webpack-built code