自动链接

searchPaths

一个相对于应用根目录的路径列表，Expo 自动链接应在这些路径中搜索要自动链接的模块。当你的项目有自定义结构或你想从不同于node_modules的目录链接本地包时，这非常有用。你指定的路径仍然必须像node_modules目录一样结构化。

🌐 A list of paths relative to the app's root directory that Expo Autolinking should search for modules to autolink. Useful when your project has a custom structure or you want to link local packages from directories different than node_modules. The paths you specify must still be structured like node_modules directories.

{
  "expo": {
    "autolinking": {
      "searchPaths": ["../../packages"]
    }
  }
}

信息 在 SDK 54 之前，这个列表默认指向你应用的 node_modules 目录，以及单体仓库中它上层的所有 node_modules 目录。 若要恢复旧的行为，请将此列表设置为你应用的 node_modules 目录，例如：["../../node_modules", "./node_modules"]。

nativeModulesDir

相对于应用根目录的路径，Expo 自动链接应该在该路径中搜索本地模块以进行自动链接。此选项的默认值为 "./modules"。只有在需要更改本地 Expo 模块的路径时，才需要更改此选项。

🌐 A path relative to the app's root directory that Expo Autolinking should search for local modules to autolink. This option defaults to "./modules". Changing this option is only useful if you need to change the path for local Expo modules.

{
  "expo": {
    "autolinking": {
      "nativeModulesDir": "./modules"
    }
  }
}

exclude

要从自动链接中排除的包名列表。如果你不想链接某些特定平台未使用的包，以减小二进制文件的大小，这非常有用。 在 package.json 中使用以下配置将在 Android 上将 expo-random 和 third-party-expo-module 排除在自动链接之外：

🌐 A list of package names to exclude from autolinking. This is useful if you don't want to link some packages that specific platforms aren't using to reduce the binary size. The following config in package.json will exclude expo-random and third-party-expo-module from autolinking on Android:

{
  "expo": {
    "autolinking": {
      "android": {
        "exclude": ["expo-random", "third-party-expo-module"]
      }
    }
  }
}

React Native 模块也可以通过在项目根目录下创建 react-native.config.js 并将模块应排除的平台配置设置为 null 来排除。以下配置将从 Android 的自动链接中排除 library-name：

🌐 React Native modules can also be excluded by creating a react-native.config.js in the root directory of your project and setting the platform's configuration that the module should be excluded from to null. The following config will exclude library-name from autolinking on Android:

module.exports = {
  dependencies: {
    'library-name': {
      platforms: {
        android: null,
      },
    },
  },
};

信息 在 SDK 54 之前，exclude 选项仅适用于 Expo 模块，而不适用于 React Native 模块。React Native 模块只能通过在项目根目录下使用 react-native.config.js 文件来排除。

flags

CocoaPods 标志，用于传递给每个自动链接的 Pod。inhibit_warnings 很可能是大多数开发者唯一想使用的标志，用于抑制在编译自动链接模块时产生的 Xcode 警告。 你可以参考 CocoaPods Podfile 文档 了解可用的标志。

🌐 CocoaPods flags to pass to each autolinked pod. inhibit_warnings is likely the only flag most developers want to use, to inhibit Xcode warnings produced when compiling the autolinked modules. You can refer to the CocoaPods Podfile documentation for available flags.

use_expo_modules!({
  flags: {
    :inhibit_warnings => false
  }
})

{
  "expo": {
    "autolinking": {
      "ios": {
        "flags": {
          "inhibit_warnings": true
        }
      }
    }
  }
}

buildFromSource

要选择不使用预构建 Expo 模块的包名称列表。完整参考，请参见 Android 的预构建 Expo 模块。

🌐 A list of package names to opt out of prebuilt Expo modules. For complete reference, see Prebuilt Expo Modules for Android.

legacy_shallowReactNativeLinking

在解析你的应用的 React Native 模块时，Expo 自动链接会搜索你应用的依赖，以及这些依赖的依赖，递归进行（符合 Node.js 解析算法）。在 SDK 54 之前，Expo 自动链接不会递归搜索依赖，只会解析你应用的直接依赖。

🌐 When resolving your app's React Native modules, Expo Autolinking searches your app's dependencies, and those dependencies' dependencies recursively (matching the Node.js resolution algorithm). Before SDK 54, Expo Autolinking didn't search dependencies recursively and only resolved your app's direct dependencies.

启用此标志后，你将选择不使用新行为，而是恢复 SDK 54 之前的行为，仅在应用的直接依赖中搜索 React Native 模块。解析 Expo 模块时不会考虑此选项。

🌐 When enabled, this flag opts you out of the new behavior and restores the behavior from before SDK 54, only searching your app's direct dependencies for React Native modules. This option isn't considered when resolving Expo modules.

search

此命令由构建系统调用，用于在自动链接的第一阶段解析 Expo 模块。其实现是在所有平台之间共享的。search 的输出将包含每个包的 duplicates 列表，如果发现有重复项的话。

🌐 This command is called by the build system to resolve Expo modules during the first phase of autolinking. Its implementation is shared between all platforms. The output from search will contain a list of duplicates per package, if any duplicates were found.

上述命令返回一个 JSON 格式的对象，其中包含 Expo Autolinking 找到的 Expo 模块：

🌐 The above command returns an object in JSON format with Expo modules that Expo Autolinking found:

{
  "expo-random": {
    "path": "/absolute/path/to/node_modules/expo-random",
    "version": "13.0.0",
    "config": {
      // Contents of `expo-module.config.json`
    },
    "duplicates": [
      // List of conflicting duplicates for this module (with lower precedence)
    ]
  }
  // more modules...
}

resolve

此命令在自动链接的第二阶段由构建系统调用。它为每个 Expo 模块输出一个包含更多（平台特定）详细信息的对象，例如 build.gradle 或 podspec 文件的路径以及要链接的模块类。

🌐 This command is called by the build system during the second phase of autolinking. It outputs an object with more (platform-specific) details for each Expo module, such as the path to the build.gradle or podspec files and module classes to link.

例如，使用 --platform apple 选项，它会返回一个 JSON 格式的对象，其中包含一个模块数组和平台的解析详情：

🌐 For example, with the --platform apple option, it returns an object in JSON format with an array of modules and resolved details for the platform:

{
  "modules": [
    {
      "packageName": "expo-random",
      "packageVersion": "13.0.0",
      "pods": [
        {
          "podName": "ExpoRandom",
          "podspecDir": "/absolute/path/to/node_modules/expo-random/ios"
        }
      ],
      "swiftModuleNames": ["ExpoRandom"],
      "modules": ["RandomModule"],
      "appDelegateSubscribers": [],
      "reactDelegateHandlers": [],
      "debugOnly": false
    }
    // more modules...
  ]
}

verify

通过检查重复项来验证自动链接的原生模块。每个有冲突的重复安装都会显示警告。

🌐 Verifies the autolinked native modules by checking for duplicates. Warnings are shown for each conflicting, duplicate installation.

传递 --verbose 选项以列出所有自动链接的原生模块。

🌐 Pass the --verbose option to list all autolinked native modules.

react-native-config

当自动链接 React Native 模块时，构建系统会调用此命令。它会输出一个对象，其中包含每个 React Native 模块的更多平台特定的详细信息，例如 gradle 或 podspec 文件的路径。

🌐 This command is called by the build system when autolinking React Native modules. It outputs an object with more platform-specific details for each React Native module, such as the path to the gradle or podspec files.

例如，使用 --platform ios 选项时，它会返回一个对象，该对象采用 react-native.config.js 的输出格式，包含每个 React Native 依赖的信息以及 React Native 安装路径。

🌐 For example, with the --platform ios option, it returns an object in react-native.config.js's output format with information about each React Native dependency and the path to the React Native installation.

{
  "root": "/absolute/path/to",
  "reactNativePath": "/absolute/path/to/node_modules/react-native",
  "dependencies": {
    "@react-native-async-storage/async-storage": {
      "root": "/absolute/path/to/node_modules/@react-native-async-storage/async-storage",
      "name": "@react-native-async-storage/async-storage",
      "platforms": {
        "ios": {
          "podspecPath": "/absolute/path/to/node_modules/@react-native-async-storage/async-storage/RNCAsyncStorage.podspec",
          "version": "",
          "configurations": [],
          "scriptPhases": []
        }
      }
    }
    // more modules...
  }
}