Hot to configure metro for EAS builds?

## 💬 Question

I am trying to use [`@ui-kitten/metro-config`](https://akveo.github.io/react-native-ui-kitten/docs/guides/improving-performance#improving-performance) with the new [EAS build](https://docs.expo.dev/build/introduction/) flow from Expo.

Everything works well when I build an app for development and serve it through a development client. However, when I build a standalone version, the custom mapping I defined through my `mapping.json` does not get applied.

The documentation linked above says that one would have to run a CLI command before building in a CI environment: `ui-kitten bootstrap @eva-design/eva ./path-to/mapping.json`. But I can't figure out where to place this command so that it gets executed on EAS build servers at the right time. The CLI command is not available even after I install `@ui-kitten/metro-config` in the project directory as a development dependency. I think the documentation isn't very clear on this.

Here is a reproducible example: https://github.com/acrdlph/expo-mcve/tree/ui-kitten - in development builds (which depend on a dev client) the `h1` size is re-defined according to the `mapping.json`. In the preview and production profiles the `h1` tag defaults back to its normal size.

(I posted this [question on StackOverflow, too](https://stackoverflow.com/questions/70498139/hot-to-configure-metro-for-ui-kitten-build-in-eas-ci), but no responses so far - hence turning to you here 🙏)

## UI Kitten and Eva version

| Package | Version |
| ----------- | ----------- |
| @eva-design/eva | 2.1.1 |
| @ui-kitten/components | 5.1.1 |