Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: upgrade to Expo SDK 52 #2843

Merged
merged 16 commits into from
Dec 10, 2024
Merged

feat: upgrade to Expo SDK 52 #2843

merged 16 commits into from
Dec 10, 2024

Conversation

frankcalise
Copy link
Contributor

@frankcalise frankcalise commented Nov 14, 2024

Please verify the following:

  • yarn test jest tests pass with new tests, if relevant
  • yarn lint eslint checks pass with new code, if relevant
  • yarn format:check prettier checks pass with new code, if relevant
  • README.md (or relevant documentation) has been updated with your changes
  • If this affects functionality there aren't tests for, I manually tested it, including by generating a new app locally if needed (see docs).

Describe your PR

  • Upgrades to Expo SDK 52 and react-native 0.76.2
  • General upgrade commands were:
yarn add@expo^52.0.0
npx expo install --fix

CLI

  • Removes New Architecture question from experimental flag, can use --newArch

Boilerplate

  • Updates Expo packages as per npx expo install --fix
  • Reworks expo-splash-screen configuration via config plugin (as recommended) over app.json splash keys
  • Remove react-native-drawer-layout patch now that v4 was released
  • Update react-native-mmkv version for new architecture to be compatible with react-native 0.76.x
  • Updates new arch flag at root expo key in app.json instead of build properties plugin as per changelog

@frankcalise frankcalise mentioned this pull request Nov 19, 2024
@frankcalise frankcalise linked an issue Nov 19, 2024 that may be closed by this pull request
@frankcalise frankcalise marked this pull request as ready for review November 22, 2024 14:30
@@ -26,6 +26,8 @@ module.exports = {
},
],
"@typescript-eslint/no-var-requires": 0,
"@typescript-eslint/no-require-imports": 0,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the new eslint rules from Expo turned this on, so I kept it off for consistency.

@@ -26,6 +26,8 @@ module.exports = {
},
],
"@typescript-eslint/no-var-requires": 0,
"@typescript-eslint/no-require-imports": 0,
"@typescript-eslint/no-empty-object-type": 0,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the new eslint rules from Expo turned this on. I disabled it because we use this pattern quite a bit with some of the MST helpers.

@RyanGst
Copy link

RyanGst commented Dec 7, 2024

First of all, thank you so much for this @frankcalise

For anyone (just like me) wondering to get expo sdk 52 working:

npx ignite-cli@latest new MyApp
yarn add expo@^52.0.0
npx expo install --fix

Enable new arch and run expo prebuild

#2847 (comment)

add this to your app.json:

{
  "expo": {
    "newArchEnabled": true
  }
}

and then run

npx expo prebuild --clean && npx expo run:android

Copy link
Member

@jamonholmgren jamonholmgren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:goberserk:

@frankcalise frankcalise merged commit fc2b357 into master Dec 10, 2024
1 check passed
@frankcalise frankcalise deleted the feat/expo-sdk-52 branch December 10, 2024 22:38
infinitered-circleci pushed a commit that referenced this pull request Dec 10, 2024
# [10.1.0](v10.0.5...v10.1.0) (2024-12-10)

### Features

* upgrade to Expo SDK 52 ([#2843](#2843) by [@frankcalise](https://github.com/frankcalise)) ([fc2b357](fc2b357)), closes [#2856](#2856) [#2862](#2862)
@infinitered-circleci
Copy link

🎉 This PR is included in version 10.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue: Compatibility Problem with react-native-mmkv 3.x.x and Ignite Boilerplate Sdk 52
7 participants