@expo/config-types 54.0.3 → 54.0.4

package/build/ExpoConfig.d.ts

@@ -253,6 +253,10 @@ export interface ExpoConfig {
      * Enable experimental features that may be unstable, unsupported, or removed without deprecation notices.
      */
     experiments?: {
+        /**
+         * Apply Expo Autolinking's search results to Metro's module resolution. This forces your project's dependencies on `react`, `react-dom`, and `react-native`, and the autolinked versions of any Expo and React Native modules to be resolved when bundling your app. This prevents version misalignment and is useful for monorepos and to prevent conflicts.
+         */
+        autolinkingModuleResolution?: boolean;
         /**
          * Export a website relative to a subpath of a domain. The path will be prepended as-is to links to all bundled resources. Prefix the path with a `/` (recommended) to load all resources relative to the server root. If the path **does not** start with a `/` then resources will be loaded relative to the code that requests them, this could lead to unexpected behavior. Example '/subpath'. Defaults to '' (empty string).
          */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@expo/config-types",
-  "version": "54.0.3",
+  "version": "54.0.4",
   "description": "Types for the Expo config object app.config.ts",
   "types": "build/ExpoConfig.d.ts",
   "main": "build/ExpoConfig.js",
@@ -37,11 +37,11 @@
     "build"
   ],
   "devDependencies": {
-    "expo-module-scripts": "^5.0.2",
+    "expo-module-scripts": "^5.0.3",
     "json-schema-to-typescript": "^14.0.5"
   },
   "publishConfig": {
     "access": "public"
   },
-  "gitHead": "475cdabd3faad56f0e8c4abcaaf21140c01c094f"
+  "gitHead": "f2270a4447fa0939e0d6f95c92bf5238e7162a73"
 }