Setting the file. One moment.
Subchapter 15.4
references/module-config.mdMarkdown2 KBView on GitHub
Use expo-module.config.json for autolinking and module registration.
File placement depends on the module type:
package.jsonexpo.autolinking.nativeModulesDir, or modules/ by default)Example:
{
"platforms": ["android", "apple", "web"],
"apple": {
"modules": ["MyModule"],
"appDelegateSubscribers": ["MyAppDelegateSubscriber"]
},
"android": {
"modules": ["expo.modules.mymodule.MyModule"]
}
}| Field | Description |
|---|---|
platforms | Array of supported platforms. Valid values include android, apple, web, and devtools. You can also use granular Apple platforms such as ios, macos, and tvos, but apple is preferred when one Swift module supports multiple Apple targets. |
apple.modules | Swift module class names |
apple.appDelegateSubscribers | Swift AppDelegate subscriber class names |
android.modules | Fully-qualified Kotlin module class names (package + class) |
Expo autolinking automatically discovers and links modules that have expo-module.config.json. No manual native project configuration needed — install via npm, run pod install.
modules directory or nativeModulesDir if defined.react-native.config.jssearchPaths directoriesnativeModulesDir (defaults to ./modules/)