| #
d42dd5d4 |
| 09-Feb-2023 |
Cedric van Putten <[email protected]> |
feature(cli): add experimental metro config telemetry (#20885)
# Why
We need to have visibility on what experimental features are being used,
in order to prioritize supporting or finishing these
feature(cli): add experimental metro config telemetry (#20885)
# Why
We need to have visibility on what experimental features are being used,
in order to prioritize supporting or finishing these features.
# How
Added a telemetry event when instantiating Metro, for both `npx expo
start` and `npx expo export`.
# Test Plan
See added test, if a property isn't available, it doesn't matter.
# Checklist
<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->
- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).
---------
Co-authored-by: Expo Bot <[email protected]>
show more ...
|