Add ability to use environment variables from .env file

[EricZeiberg]

Description
Radon IDE allows users to manually set environment variables in the build using the env: {} field in the config JSON, but a lot of common workflows involve storing environment variables in a .env file, so it would be very helpful if there was a way to specify a file instead of having the keys live in the config.

Environment

• Version of currently used Radon IDE: 1.0
• Version of React Native/Expo used in the project: 0.78

[kmagiera]

Thanks for reporting.

I'm not sure if I understand this right. Not sure if you're referring here to some tools like react-native-dotenv to be able to access that (in which case I think this should just work) or you actually want the build comands to use environment variables from that .env file.

In case of the latter, I'd be curious to learn how this is used in workflows where Radon IDE isn't involved (e.g. from command line when you use expo or rn-cli). I know that some toolchains for other languages use this concept of .env but I am not aware of any standard nor typical scenario where this would be used by React Native specific tooling. So given you use that you must have some shell-like environment setup in a way to include .env or perhaps have that specified in package.json scripts section?