It's now built against React 16.11 (React Native's update post also does a bad job at this)
Node 13 is no longer supported (expo-cli), upgrade to 14 (not that related, but important nonetheless)
It would be super helpful to have a list of updated native modules, as many of us were waiting for a specific fix to land. Here is the list as I use them (so not all of them) and I hope this helps someone:
Let everyone know your app is universal with Expo!
[](https://expo.io/)
[](https://expo.io/)
👏 Contributing
If you like the Expo CLI and want to help make it better then check out our contributing guide! Also check out the Expo repo to work on the Expo docs, modules, and components in the…
we started leaving this list out because the blog post becomes quite long, so we link to the changelog instead. also, we update everything automatically when you run expo upgrade, except for the types.. we should add that!
Yep, expo upgrade finally worked smoothly (I had issues with 36 -> 37, 35 -> 36), so very happy with that. If this list was in the Changelog, that would work for me as well.
EDIT: expo upgrade upgraded react-native-screens to ~2.8.0, but it gave me a warning that it expected version range: ~2.9.0 - actual version installed: ~2.8.0. (expo install worked fine, just the upgrade).
The use case that's not covered if it's not listed anywhere is that quite a few times I've not added a module because there were issues with it (resolved upstream, waiting for next SDK) and I could then instantly see "ah it got bundled".
^^^
I'm just lazy ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Missing in this post (for me):
@react-native-community/masked-view0.1.60.1.10expo~37.0.12^38.0.3expo-linear-gradient~8.1.0~8.2.1expo-secure-store~8.1.0~9.0.1expo-splash-screen^0.2.3~0.3.1expo-web-browser~8.2.1~8.3.1react16.9.016.11.0react-dom16.9.016.11.0react-native-maps0.26.10.27.1react-native-reanimated~1.7.1~1.9.0react-native-safe-area-context0.7.33.0.2react-native-screens~2.2.0~2.8.0react-native-svg11.0.112.1.0react-native-webview8.1.19.4.0Additionally update your types:
@types/react-native~0.61.23~0.62.13Why do you say node 13 is not suppprted? I looked in the repo and the engines field is set to > 6.x
Check out these lines in the
expo-clirepo:Tools for creating, running, and deploying Universal Expo and React Native apps
Expo CLI
Tools for creating, running, and deploying Universal Expo and React Native apps
📚 Read the Documentation | Contributing to Expo CLI
Learn about building and deploying universal apps in our official docs!
Let everyone know your app is universal with Expo!
If you like the Expo CLI and want to help make it better then check out our contributing guide! Also check out the Expo repo to work on the Expo docs, modules, and components in the…
Gotcha thanks, and good to know
As for now it is not, the most stable node is v12.18.1
No, it won't be supported, because uneven node versions never become LTS. The "less stable" (current) version of 14.x works fine with expo :)
we started leaving this list out because the blog post becomes quite long, so we link to the changelog instead. also, we update everything automatically when you run
expo upgrade, except for the types.. we should add that!other points are useful too! thank you!
Yep,
expo upgradefinally worked smoothly (I had issues with 36 -> 37, 35 -> 36), so very happy with that. If this list was in the Changelog, that would work for me as well.EDIT:
expo upgradeupgradedreact-native-screensto~2.8.0, but it gave me a warning that it expected version range:~2.9.0- actual version installed:~2.8.0. (expo installworked fine, just the upgrade).The use case that's not covered if it's not listed anywhere is that quite a few times I've not added a module because there were issues with it (resolved upstream, waiting for next SDK) and I could then instantly see "ah it got bundled".
^^^
I'm just lazy ;)