How should we handle a lot of envs in app.config.js(ts)?

[t6adev]

Hi there,

Previously, I've created app.json every time when running expo/building app.
I'm trying to use app.config.ts(the doc) instead of app.json to switch envs.
Our project has a lot of envs, so I've been using JSON files to build config content instead of using the dotenv library straightforwardly. This means it's used fs.readFileSync in the file.

But I realized the app.config.ts is called multiple times when running expo start.
In the config, I write console.log() so a lot of logs show up when running expo. So annoying but I want to show the app config built once.

My questions are:

• The way is not a good way?
• Is the way acceptable in the build process? ($ expo build / $ eas build)
• How do you handle a lot of envs?
• I want to show the app config built in the terminal. What should I do?

Thanks.

[t6adev]

To prevent showing up a lot of console.log(), I used process.env.ONCE_FLAG in my app.config.ts.
Currently, there is nothing a problem with my idea 👍