next.js/examples/with-universal-configuration-build-time/pages/index.js

export default () => (
  <div>
    <p>Environment variable process.env.VARIABLE_EXAMPLE is "{process.env.VARIABLE_EXAMPLE}"</p>
    <p>Custom environment variables process.env.BACKEND_URL is "{process.env.BACKEND_URL}"</p>
  </div>
)
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 19:19:31 +00:00			`export default () => (`
			`<div>`
			`<p>Environment variable process.env.VARIABLE_EXAMPLE is "{process.env.VARIABLE_EXAMPLE}"</p>`
			`<p>Custom environment variables process.env.BACKEND_URL is "{process.env.BACKEND_URL}"</p>`
			`</div>`
			`)`