Compiled build inlines PORT environment variable

Due to how getClientEnvironment is written, PORT environment variable is being inlined into final build instead of being kept as process.env.PORT.

This will cause Razzle to fail launching on Heroku using start:prod

[ericvicenti]

I found a pretty simple workaround to this issue, if people are still struggling with it

  // This will extract the env during production execution.. PORT will not be inlined during build
  const getEnv = c => process.env[c];
  app.listen(getEnv('PORT'));

[JacopKane]

This is my workaround for Heroku:

// getPorts.js

// bypass webpack.DefinePlugin
const { env } = require('process')

export const port = () =>
  parseInt(
    env.RAZZLE_PORT ||
      env.PORT ||
      process.env.RAZZLE_PORT ||
      process.env.PORT ||
      3000,
    10,
  )