run `next start` in different environment variable

[khrome83]

How do we run next start with a different environment variable?

Right now it is set to production automatically. But in staging and development servers I would like to give it a different environment variable, because analytics requires a different include.

Is there a way to override the default behavior or next start?

[timneutkens]

Please see these 2 files. Setting NODE_ENV to production is just a default. You can override it.
https://github.com/zeit/next.js/blob/master/bin/next-build#L8
NODE_ENV=staging next build
https://github.com/zeit/next.js/blob/master/bin/next-start#L8
NODE_ENV=staging next start

[sarkistlt]

Hi, I still quit didn't get it what to override?

[schoenwaldnils]

@timneutkens why do you read the NODE_ENV from the arguments that are provided to the script?
and not from process.env?

This results in an inconvenient duplicate in my travis file

- NODE_ENV=shared
- if [[ ! -z $TRAVIS_TAG ]] && [[ $TRAVIS_TAG =~ ^v.*$ ]]; NODE_ENV=production; fi
- NODE_ENV=$NODE_ENV npm run next-export

(npm run next-export calls next build && next export)