@lotics/ui 1.3.0 → 1.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/ui",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "type": "module",
   "exports": {
     "./tokens": "./src/tokens.ts",

package/src/dom_portal.ts

@@ -0,0 +1,20 @@
+import type { ReactNode, ReactPortal } from "react";
+
+/**
+ * Native stand-in for `react-dom`'s `createPortal`.
+ *
+ * `Portal` only calls `createPortal` inside its web (`isWeb`) branch, so on
+ * React Native this is never invoked. The file exists purely so the shared
+ * `portal.tsx` can `import { createPortal }` statically without pulling
+ * `react-dom` — which has no native build — into the Metro native bundle.
+ *
+ * Web targets resolve `dom_portal.web.ts` instead (Metro's `.web` extension
+ * resolution; Vite's `resolve.extensions`).
+ */
+export function createPortal(
+  _children: ReactNode,
+  _container: Element | DocumentFragment,
+  _key?: string | null,
+): ReactPortal | null {
+  return null;
+}

package/src/dom_portal.web.ts

@@ -0,0 +1,8 @@
+/**
+ * Web variant: the real `react-dom` portal. Isolated into its own module so
+ * the native bundle (which resolves `dom_portal.ts`) never references
+ * `react-dom`. Imported statically by `portal.tsx` — no `require`, so it
+ * works under pure-ESM bundlers (Vite, used by custom-code apps) as well as
+ * Metro.
+ */
+export { createPortal } from "react-dom";

package/src/portal.tsx

@@ -11,6 +11,7 @@ import {
   ReactNode,
 } from "react";
 import { Platform, View, StyleSheet } from "react-native";
+import { createPortal } from "./dom_portal";
 
 /**
  * Cross-platform portal system inspired by Base UI and @gorhom/portal.
@@ -137,8 +138,6 @@ export function Portal({ children }: { children: ReactNode }) {
       return null;
     }
 
-    // eslint-disable-next-line @typescript-eslint/no-require-imports
-    const { createPortal } = require("react-dom");
     return createPortal(children, target);
   }