UNPKG

1.33 kBJavaScriptView Raw
1// We make some of the Expo SDK available on a global in order to make it
2// possible to augment their libraries with some Expo-specific behavior
3// when inside of an environment with the Expo SDK present, but otherwise
4// continue to work in any bare React Native app without requiring that
5// they install the 'expo' package. We can get rid of this entirely when
6// the following RFC has been implemented:
7// https://github.com/react-native-community/discussions-and-proposals/issues/120
8Object.defineProperties(module.exports, {
9 Asset: {
10 enumerable: true,
11 get() {
12 return require('expo-asset').Asset;
13 },
14 },
15 Constants: {
16 enumerable: true,
17 get() {
18 return require('expo-constants').default;
19 },
20 },
21 Font: {
22 enumerable: true,
23 get() {
24 return require('expo-font');
25 },
26 },
27 Icon: {
28 enumerable: true,
29 get() {
30 return require('@expo/vector-icons');
31 },
32 },
33 LinearGradient: {
34 enumerable: true,
35 get() {
36 return require('expo-linear-gradient').LinearGradient;
37 },
38 },
39 SQLite: {
40 enumerable: true,
41 get() {
42 return require('expo-sqlite').SQLite;
43 },
44 },
45});
46//# sourceMappingURL=globals.js.map
\No newline at end of file