| #
8a424beb |
| 11-Aug-2023 |
James Ide <[email protected]> |
[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 ...
|
| #
0381251e |
| 12-Jul-2023 |
Tomasz Sapeta <[email protected]> |
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]>
show more ...
|
| #
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 ...
|