[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)Why --- Prettier 3 is out. Add support for it with this linter config. **Note for reviewer:** the first commit is the one with th
[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)Why --- Prettier 3 is out. Add support for it with this linter config. **Note for reviewer:** the first commit is the one with the actual changes. The rest of this PR are changes to get the linter passing (mostly autofix). How --- Update eslint-config-prettier and eslint-plugin-prettier. To address deprecation warnings, also update typescript-eslint/parser and typescript-eslint/eslint-plugin. Because of an update to typescript-eslint/parser, we need to suppress deprecation warnings (documented in a comment). Regenerated test snapshots. Due to the upgraded dependencies, typecasts and optional chaining are now auto-fixable by lint. This converts warnings into autofixes. Test Plan --- `yarn test` in the linter config. Run `expotools check --all --fix-lint --no-build --no-test --no-uniformity-check` to try this config on the whole repo. --------- Co-authored-by: Expo Bot <[email protected]>
show more ...
Update react-native to 0.72.2 (#23476)# Why Updating RN to 0.72.2 # How - Updated the submodule - Updated versions in dependencies (including templates) - Updated Podfile locks # Test
Update react-native to 0.72.2 (#23476)# Why Updating RN to 0.72.2 # How - Updated the submodule - Updated versions in dependencies (including templates) - Updated Podfile locks # Test Plan Checked if bare-expo builds and quickly ran through some tests and examples – all seem good. --------- Co-authored-by: Tomasz Sapeta <[email protected]> Co-authored-by: Brent Vatne <[email protected]>
feat(cli): auto enable --dev-client in `npx expo start` (#22926)# Why - related https://github.com/expo/expo/pull/22924 https://github.com/expo/expo/pull/22925 https://github.com/expo/expo/pul
feat(cli): auto enable --dev-client in `npx expo start` (#22926)# Why - related https://github.com/expo/expo/pull/22924 https://github.com/expo/expo/pull/22925 https://github.com/expo/expo/pull/22890 - Use a basic heuristic to auto enable `--dev-client` when `expo-dev-client` is in the project `package.json`. Users can swap to Expo Go with `s` or pass `--go` to ensure Expo Go is the default target. # Test Plan - Added basic option tests. - Updated the docs. --------- Co-authored-by: Expo Bot <[email protected]>
fix(cli): only check if `unstable_serverRoot` is defined (#21263)# Why We only need to check if this property is defined or not. # How Changed it into a boolean # Test Plan <!-- Ple
fix(cli): only check if `unstable_serverRoot` is defined (#21263)# Why We only need to check if this property is defined or not. # How Changed it into a boolean # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # 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).
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]>
fix(cli): fix rudderstack anonymous ID generation in dev-client start command (#18584)
feat(cli): add telemetry event tracking a command run (#17948)* add telemetry event tracking a command run * Ensure user authenticated * Update rudderstackClient.ts * Update rudderstackCli
feat(cli): add telemetry event tracking a command run (#17948)* add telemetry event tracking a command run * Ensure user authenticated * Update rudderstackClient.ts * Update rudderstackClient.ts * Update CHANGELOG.md
[cli] Add CI info to telemtry (#17284)* [cli] Add CI info to telemtry * (changelog)
chore(cli): lazy load all env vars (#17082)* chore(cli): lazy load all env vars lazily loading all environment variables makes it easier to test different cases since you can change the value of
chore(cli): lazy load all env vars (#17082)* chore(cli): lazy load all env vars lazily loading all environment variables makes it easier to test different cases since you can change the value of things like `CI` between tests. * Update packages/@expo/cli/CHANGELOG.md Co-authored-by: Expo Bot <[email protected]> Co-authored-by: Expo Bot <[email protected]>
chore: refactor `expo/cli` to `@expo/cli` package (#16717)* chore: refactor `expo/cli` to `@expo/cli` package * Update CODEOWNERS * fix linking * fix lint script * fix build file * f
chore: refactor `expo/cli` to `@expo/cli` package (#16717)* chore: refactor `expo/cli` to `@expo/cli` package * Update CODEOWNERS * fix linking * fix lint script * fix build file * fix e2e tests * lint before build * use mock version