Expo SDK 41 rolled out an interface called config plugins which lets users add native modules that aren't in the Expo Go app to their native cloud builds and locally when prebuilding.
We're using this package in a project so I've added plugin config for it in the hopes of avoiding the need to eject
How
Added a app.plugin.js as the main entry point to the plugin. Plugins must run in at node LTS environments (currently that means 12 and greater).
Test Plan
Run npm pack in the package
Install the package in a managed Expo project yarn add @ovalmoney/react-native-fitness@../react-native-fitness/ovalmoney-react-native-fitness-0.5.3.tgz
Then add "@ovalmoney/react-native-fitness" to the plugins array and build the native app locally with expo prebuild and yarn ios, yarn android.
App built correctly without any errors.
Running expo config --type introspect showed all of the desired config changes in AndroidManifest, Info.plist, and entitlements files.
Why
Expo SDK 41 rolled out an interface called config plugins which lets users add native modules that aren't in the Expo Go app to their native cloud builds and locally when prebuilding.
We're using this package in a project so I've added plugin config for it in the hopes of avoiding the need to eject
How
Added a app.plugin.js as the main entry point to the plugin. Plugins must run in at node LTS environments (currently that means 12 and greater).
Test Plan
npm packin the packageyarn add @ovalmoney/react-native-fitness@../react-native-fitness/ovalmoney-react-native-fitness-0.5.3.tgzexpo prebuildandyarn ios,yarn android.expo config --type introspectshowed all of the desired config changes in AndroidManifest, Info.plist, and entitlements files.