rsnext/examples/with-universal-configuration-build-time/env-config.js

const prod = process.env.NODE_ENV === 'production'

module.exports = {
  'process.env.BACKEND_URL': prod
    ? 'https://api.example.com'
    : 'https://localhost:8080',
  'process.env.VARIABLE_EXAMPLE': process.env.VARIABLE_EXAMPLE
}
Added universal configuration example (#991) * Added universal configuration example * Make example more clear 2017-02-05 00:13:23 +01:00			`const prod = process.env.NODE_ENV === 'production'`

			`module.exports = {`
Add prettier for examples directory (#5909) * Add prettier for examples directory * Fix files * Fix linting * Add prettier script in case it has to be ran again 2018-12-17 17:34:32 +01:00			`'process.env.BACKEND_URL': prod`
			`? 'https://api.example.com'`
Modify with-universal-configuration example (#4498) (#5948) Explains in details how the "with-universal-configuration" example works and rename it to "with-universal-configuration-build-time". Changing the example name makes the purpose of the example clear. The "env-config.js" file introduce one more sample of variable usage that instantiates an immediate value of the local environment variable. This makes it even clearer how build-time variable configuration works. The "index.js" page makes explicit the use of these configured environment variables. The universal configuration confusion happens when the value of the environment variable is used directly in the application causing an effect in server-side but not on the client side. 2018-12-26 20:19:31 +01:00			`: 'https://localhost:8080',`
			`'process.env.VARIABLE_EXAMPLE': process.env.VARIABLE_EXAMPLE`
Added universal configuration example (#991) * Added universal configuration example * Make example more clear 2017-02-05 00:13:23 +01:00			`}`