Fix web build: shim react-native-tcp-socket for web platform

Metro resolves require() calls statically, so even though NativeSocketProvider
is never instantiated on web, the require('react-native-tcp-socket') still
causes a build failure during expo export --platform web.

Added a web shim at src/shims/react-native-tcp-socket.ts and configured
Metro's resolveRequest to redirect the import on web platform.

Author: NateIsern

metro.config.js

@@ -5,7 +5,6 @@ const path = require("path");
 const config = getDefaultConfig(__dirname);
 
 // Inject crypto polyfill AFTER the default pre-main modules.
-// The default includes React Native's InitializeCore which MUST come first.
 const originalGetModules =
   config.serializer?.getModulesRunBeforeMainModule ??
   (() => []);
@@ -21,10 +20,28 @@ config.serializer = {
   },
 };
 
-// Support .wasm files as assets (needed for expo-sqlite web support)
+// Support .wasm files as assets (needed for expo-sqlite web support).
+// Redirect native-only modules to shims when bundling for web.
+const TCP_SHIM = path.resolve(__dirname, "src/shims/react-native-tcp-socket.ts");
+
+const originalResolveRequest = config.resolver?.resolveRequest;
+
 config.resolver = {
   ...config.resolver,
   assetExts: [...(config.resolver?.assetExts ?? []), "wasm"],
+  resolveRequest(context, moduleName, platform) {
+    // On web, replace react-native-tcp-socket with an empty shim
+    if (platform === "web" && moduleName === "react-native-tcp-socket") {
+      return {
+        type: "sourceFile",
+        filePath: TCP_SHIM,
+      };
+    }
+    if (originalResolveRequest) {
+      return originalResolveRequest(context, moduleName, platform);
+    }
+    return context.resolveRequest(context, moduleName, platform);
+  },
 };
 
 module.exports = withNativeWind(config, { input: "./global.css" });

src/shims/react-native-tcp-socket.ts

@@ -0,0 +1,14 @@
+/**
+ * Web shim for react-native-tcp-socket.
+ * 
+ * This file is resolved instead of the real native module when bundling for web.
+ * TCP sockets are not available in browsers - the FallbackSocketProvider handles
+ * this gracefully at runtime.
+ */
+
+// Re-export an empty object - the NativeSocketProvider is never instantiated on web
+export default {
+  createConnection() {
+    throw new Error("TCP sockets are not available on web platform");
+  },
+};