process.env (or other globals) support

Node, Webpack and React communities adopted the use of process.env to setup build time variables.

Examples:

process.env.PUBLIC_URL = 'https://react-something.stackblitz.io'
process.env.NODE_ENV = 'production'

Is there a way to configure those automatically?

[goleary]

I see, thanks!

This is where I initially looked to see if I could set them:

Perhaps an “Environment Config” section that enables setting env variables?

[diarmuidoconnor]

Hi, Concerning the declaration of custom environment variables, I require to declare an API key value for a React app. When using the create-react-app tool on localhost, the typical solution is to use the .env file. This approach does not work on the template React app environment created by Stackblitz, which uses the EngineBlock model (as opposed to Web Container), as I understand it. When running on localhost, the keys declared in .env are accessed by a React component using the process.env object. This object is also present in the StackBlitz environment and has one default property, NODE_ENV. However, any variables declared in .env are not added to process.env.

Has anyone come up with a workaround for this problem? Tks