Closed rossb89 closed 5 years ago
Thanks, @rossb89! Is expo-constants
a separate npm package that needs to be included? or does it come automatically with the expo
package?
Yes, you have to manually install expo-constants
.
Best to use the new expo install
command as it take care of your expo version.
So, I think expo-constants
is missing in the package.json
at the moment
Good point.
Seems as well now that if your Expo app is not 'managed' and is using the 'Bare' workflow (i.e an 'ejected' expo app, or react native app that wants to use the Expo API's), then you need to follow more installation instructions to get react-native-unimodules installed in order to use the new separate packages.
On my managed Expo install, after using expo install expo-constants
it's added `"expo-constants": "^5.0.1", so I guess this does need to be in the package.json... i'll add it in.
By the way - Is there a reason why the dependencies are listed under devDependencies instead of dependencies? :)
Thanks, @rossb89! Once that change is submitted I'll approve, merge, and publish a new version.
@ryanvanderpol Added into package.json now 👍
Thanks! Merging and publishing shortly.
This is now published via npm as 1.0.9. Thanks everyone for your help!
Hi there,
Expo v33 has deprecated the use of imports like this from the 'expo' package. https://blog.expo.io/expo-sdk-v33-0-0-is-now-available-52d1c99dfe4c#b331
e.g.
import { Constants } from 'expo'
A lot of noise gets generated because of this now in the terminal.
This 1 line change is all that's required for v33 compatibility, although it would cause an issue for anyone on expo < v33 so perhaps a version bump is needed :)