eas.config.js support
Brent Vatne
we don't plan to support this because eas.json is not meant to contain complex configuration. i would suggest swapping out the eas.json when needed for your multi tenant apps. however, if you can outline in more detail how this might help, that could be helpful for us to consider the request
Nils
Brent Vatne sure. We are having a Single repository for out App. We Sell our App to our Customer and configure Most of the content via the backend. In Order to not have 420 repositories or Branches for Esch Customer it would be Rasier for us to manage things directly in the specific file. Otherwise we would need to generate the file every time before EAs build/submit. As the nice app.json supports this awesome feature, why not eas.json? All benefits which are applicable for app.json can also be applied for eas.json