expo-desktop 0.1.30 → 0.1.31

package/build/create-app/create-expo-desktop-app.js

@@ -98,7 +98,6 @@ export async function createExpoDesktopApp({ localDev, name, packageManager, tem
     }
     title("Adding Expo support to the Metro config…", { spacing: 1 });
     await improveMetroConfig({ projectPath });
-    await addWindowsExpoPolyfill({ projectPath });
     title("Adding Expo support to the Babel config…", { spacing: 1 });
     await writeBabelConfig({ projectPath });
 }
@@ -472,17 +471,6 @@ const { getDefaultConfig } = require("@expo/metro-config");
 const { makeMetroConfig } = require("@rnx-kit/metro-config");
 
 const config = makeMetroConfig(getDefaultConfig(__dirname));
-
-const getPolyfills = config.serializer.getPolyfills;
-const windowsExpoPolyfill = require.resolve("./expo-polyfill.windows.js");
-config.serializer.getPolyfills = (...args) => {
-  const polyfills = getPolyfills(...args);
-  if (args[0].platform === "windows") {
-    polyfills.push(windowsExpoPolyfill);
-  }
-  return polyfills;
-};
-
 module.exports = config;
     `.trim() + "\n", "utf-8");
     }
@@ -492,69 +480,6 @@ module.exports = config;
     }
     console.log(`\n${green("◆")}  Overwrote metro.config.js.\n`);
 }
-/**
- */
-async function addWindowsExpoPolyfill({ projectPath }) {
-    await fs.writeFile(path.resolve(projectPath, "expo-polyfill.windows.js"), `
-try {
-  // Until we can configure TurboModules for eager initialisation (which is
-  // waiting on https://github.com/microsoft/react-native-windows/pull/16093), we
-  // need to trigger the lazy-init of our TurboModule by accessing it for the
-  // first time, which causes the TurboModuleManager to call its REACT_INIT
-  // method.
-  //
-  // We can't do any imports inside getPolyfills(), but can use the global proxy:
-  globalThis.nativeModuleProxy.ExpoMainRuntimeInstaller;
-
-  // TODO: Implement Expo's NativeModulesProxy and make all of this
-  //       lazy-initialised (and actually populate \`exportedMethods\`, etc.).
-
-  // Below are temporary stubs to suppress these warnings:
-  //  WARN  The "EXNativeModulesProxy" native module is not exported through NativeModules; verify that expo-modules-core's native code is linked properly
-  //  WARN  No native ExponentConstants module found, are you sure the expo-constants's module is linked properly?
-  //  WARN  No native ExponentConstants module found, are you sure the expo-constants's module is linked properly?
-
-  // Funnily enough, although expo-modules-core prefers to access
-  // global.expo?.modules?.NativeModulesProxy over the deprecated
-  // NativeModules?.NativeUnimoduleProxy, we still need the latter to exist in
-  // order for it to check the former. And it's only
-  globalThis.nativeModuleProxy.NativeUnimoduleProxy;
-  const { ExpoAsset } = globalThis.nativeModuleProxy;
-
-  const ExponentConstants = {};
-
-  globalThis.expo.modules = {
-    ExpoAsset,
-    ExponentConstants,
-    // - JS: apps/demo/node_modules/expo-modules-core/src/NativeModulesProxy.native.ts
-    // - iOS:
-    //   - NativeUnimoduleProxy: apps/demo/node_modules/expo-modules-core/ios/Legacy/NativeModulesProxy/NativeModulesProxyModule.swift
-    //   - NativeModulesProxy: apps/demo/node_modules/expo-modules-core/ios/Legacy/NativeModulesProxy/EXNativeModulesProxy.mm
-    // - Android:
-    //   - NativeUnimoduleProxy: apps/demo/node_modules/expo-modules-core/android/src/main/java/expo/modules/adapters/react/NativeModulesProxy.java
-    //   - NativeModulesProxy: apps/demo/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/defaultmodules/NativeModulesProxyModule.kt
-    NativeModulesProxy: {
-      exportedMethods: {
-        ExpoAsset: [],
-        ExponentConstants: [],
-      },
-      modulesConstants: {
-        ExpoAsset: [],
-        ExponentConstants: [],
-      },
-    },
-  };
-
-  // Now expo-modules-core can populate its fileprivate
-  // \`const NativeModulesProxy: Record<string, ProxyNativeModule = {}\` from our
-  // global.expo?.modules?.NativeModulesProxy. This avoids the warning about
-  // EXNativeModulesProxy being missing.
-} catch (error) {
-  console.error("Polyfill failed", error);
-  throw error;
-}
-    `.trim() + "\n", "utf-8");
-}
 async function updatePodfile({ projectPath }) {
     const appJsonPath = path.resolve(projectPath, "macos/Podfile");
     let contents;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "expo-desktop",
-  "version": "0.1.30",
+  "version": "0.1.31",
   "description": "Best-effort desktop support for Expo",
   "keywords": [
     "android",
@@ -37,8 +37,8 @@
     "@clack/prompts": "^1.2.0",
     "arktype": "^2.2.0",
     "citty": "^0.2.2",
-    "expo-desktop-config-plugins": "^1.1.27",
-    "expo-desktop-prebuild-config": "^1.0.13",
+    "expo-desktop-config-plugins": "^1.1.28",
+    "expo-desktop-prebuild-config": "^1.0.14",
     "glob": "^10.5.0",
     "kleur": "^4.1.5",
     "mustache": "^4.2.0",