Checked for removed libraries in examples per release blog (none found)
Added a quick-and-dirty upgrade-dependencies.sh script that runs expo upgrade on all projects at once and writes the command output to a non-committed folder for review (can also run expo doctor --fix-dependencies on all projects, for those times where the SDK's RN version is updated mid-PR :smile: ).
Spot-checked several projects based on a) if they failed to automatically update via the aforementioned script, b) were mentioned specifically during the previous update (https://github.com/expo/examples/pull/371), or c) otherwise seemed interesting or notable.
In some cases, updated additional dependencies and/ or readme's to reflect my experiences getting the spot-checked examples up-and-running
Made readme's consistently refer to expo start across the board due to several package.json files containing no scripts.
tweaked the npm scripts to account for removal of expo-yarn-workspaces, added separate script for watching packages (previously ran automatically after running yarn)
:white_check_mark: with-electron
I've tried adding electron at least three times in recent months, and it never works unless I run yarn expo-electron customize and add contextIsolation: false to index.js, so updated accordingly. Wondering if this should either be reflected in docs or if @expo/electron-adapter can be/ should be updated to do this by default.
:white_check_mark: with-gatsby
Kept gatsby version at 2.x, as plugin isn't compatible with 3 or 4.
This basic example works with Expo packages that are more recent than the peer deps specify in expo-three, plus a post 0.127.0 version of three, which fixes https://github.com/expo/expo-three/issues/202
:warning: with-splash-screen
Works on Android, but Updates.reloadAsync() fails silently with "You cannot reload when expo-updates is not enabled" on iOS on Expo Go (not a problem with example, issue opened)
:warning: with-nextjs
Works if I leave @expo/next-adapter/ nextjs dependencies on the same version; homepage url hangs indefinitely if I run yarn expo-next from scratch on latest adapter version (which installs next 12.x, which uses requires webpack 5, while the adapter uses 4), I get a fatal babel error if I install the required peer-dependency version of next (^11, which can use Webpack 4, but doesn't by default).
What
expo upgradeon all projects at once and writes the command output to a non-committed folder for review (can also runexpo doctor --fix-dependencieson all projects, for those times where the SDK's RN version is updated mid-PR :smile: ).expo startacross the board due to several package.json files containing noscripts.eject.Spot-checking results
:white_check_mark: with-yarn-workspaces
expo-yarn-workspaces, added separate script for watching packages (previously ran automatically after runningyarn):white_check_mark: with-electron
yarn expo-electron customizeand addcontextIsolation: falseto index.js, so updated accordingly. Wondering if this should either be reflected in docs or if@expo/electron-adaptercan be/ should be updated to do this by default.:white_check_mark: with-gatsby
gatsbyversion at 2.x, as plugin isn't compatible with 3 or 4.:white_check_mark: with-three / with-react-three-fiber
expo-three, plus a post 0.127.0 version ofthree, which fixes https://github.com/expo/expo-three/issues/202:warning: with-splash-screen
Updates.reloadAsync()fails silently with "You cannot reload when expo-updates is not enabled" on iOS on Expo Go (not a problem with example, issue opened):warning: with-nextjs
@expo/next-adapter/nextjsdependencies on the same version; homepage url hangs indefinitely if I runyarn expo-nextfrom scratch on latest adapter version (which installs next 12.x, which uses requires webpack 5, while the adapter uses 4), I get a fatal babel error if I install the required peer-dependency version of next (^11, which can use Webpack 4, but doesn't by default).:white_check_mark: with-moti
:white_check_mark: with-typescript
:white_check_mark: with-tab-navigation
:white_check_mark: with-drawer-navigation