Metro resolver recursion when separated uniwind instances are installed

[eliotgevers]

What happened?

When running a dev build via bun expo run:ios, the app crashes with an infinite recursion in Uniwind’s Metro resolver. The error is a NativeModules stack overflow. This does not happen in Expo Go (same repo, same code).

Error signature:

[runtime not ready]: RangeError: Maximum call stack size exceeded (native stack depth)
get NativeModules
get NativeModules
...

Findings / root cause hypothesis:

• Uniwind rewrites require(\"react-native\") → uniwind/components for most modules.
• Inside uniwind/components, many getters call require(\"react-native\") again (to access NativeModules, etc).
• If Uniwind fails to detect that the origin is inside Uniwind, it rewrites again → infinite loop.
• Guard currently uses:
  context.originModulePath.startsWith(cachedInternalBasePath)
• Under Bun, the path looks like:
  .../node_modules/.bun/uniwind@1.2.7/node_modules/uniwind/dist/module/components/...
  but cachedInternalBasePath is:
  .../node_modules/uniwind/dist/module
• That mismatch makes isInternal false → rewrite loop.

Suggested fix:

• Normalize paths with realpathSync (or equivalent) for both cachedInternalBasePath and originModulePath, or
• Use a package-boundary check (e.g. /node_modules/uniwind/) instead of a raw startsWith on a non-normalized path.

Steps to Reproduce

1. Clone the repo below
2. bun install
3. bun expo run:ios
4. Launch the dev build (crash occurs on startup)

Note: Expo Go does not crash.

Snack or Repository Link (Optional)

https://github.com/eliotgevers/uniwind-heroui-bun-repro

Uniwind version

1.2.7

React Native Version

0.81.5

Platforms

iOS

Expo

Yes

Additional information

• I've searched for similar issues in this repository and found none
• I am a Uniwind Pro user

[eliotgevers]

I was able to temporarily fix it in my metro.config.js:

const fs = require("fs");
const path = require("path");
const { getDefaultConfig } = require("expo/metro-config");
const { resolve } = require("metro-resolver");
const { withUniwindConfig } = require("uniwind/metro");

const config = withUniwindConfig(getDefaultConfig(__dirname), {
  cssEntryFile: "./app/globals.css",
  dtsFile: "./uniwind-types.d.ts",
});

// TEMPORARY: Fix for uniwind/metro issue
const uniwindPackageJson = fs.realpathSync(
  require.resolve("uniwind/package.json", {
    paths: [__dirname],
  }),
);
const uniwindRoot = path.dirname(uniwindPackageJson);
const uniwindResolveRequest = config.resolver?.resolveRequest;
const realpathSafe = (value) => {
  try {
    return fs.realpathSync(value);
  } catch {
    return value;
  }
};
const isUniwindInternal = (originModulePath) => {
  if (!originModulePath) return false;
  const resolvedOrigin = realpathSafe(originModulePath);
  return resolvedOrigin.startsWith(uniwindRoot + path.sep);
};

config.resolver = {
  ...config.resolver,
  resolveRequest: (context, moduleName, platform) => {
    if (moduleName === "react-native" && isUniwindInternal(context.originModulePath)) {
      return resolve(context, moduleName, platform);
    }

    if (typeof uniwindResolveRequest === "function") {
      return uniwindResolveRequest(context, moduleName, platform);
    }

    return resolve(context, moduleName, platform);
  },
};

module.exports = config;

[Brentlok]

Hi, it installed differently in my env, and it's working fine

I'm not sure how it's working, but I would guess that bun installs dependencies inside .bun directory only in monorepos. What version of bun are you using? I'm using bun@1.3.6. Do you have some additional global bun config?

[eliotgevers]

Found the issue... weird bun linking issues. Removed bun.lock entirely and removed all node modules, then ran bun install again to start fresh. For context, I was using bun@1.3.8 without bunfig, and with "configVersion": 1

Just goes to show that Uniwind is well built! Thank you for your quick responses!

[DiegoSerra]

Hi, I'm getting the same error installing it with pnpm and node-linker=hoisted (due to module federation). The temporary fix you commented works, but I would like a permanent solution. As you said this problem occurs with monorepos

[Brentlok]

Hi, I'm getting the same error installing it with pnpm and node-linker=hoisted (due to module federation). The temporary fix you commented works, but I would like a permanent solution. As you said this problem occurs with monorepos

Could you prepare a minimal repo where such issue occurs?

[DiegoSerra]

Hi, I'm getting the same error installing it with pnpm and node-linker=hoisted (due to module federation). The temporary fix you commented works, but I would like a permanent solution. As you said this problem occurs with monorepos

Could you prepare a minimal repo where such issue occurs?

https://github.com/dserra-km/universal-turbo-monorepo/tree/feature/uniwind

This is a minimal showcase with storybook, web and mobile. That's the stack I'm trying to achieve. Both storybook and web work (with module federation). But when I try to make it work for mobile, I get a Maximum call stack error as soon as I add withUniwindConfig to my metro.config (Module federation is no the problem itself). As I said, I need this npmrc configuration due to Module federation, so the only way I've seen so far is the one mentioned in metro.config.

To launch this project, you need to run "pnpm dev" and then "pnpm android" in the mobile/shell path.

[DiegoSerra]

Hi, I'm getting the same error installing it with pnpm and node-linker=hoisted (due to module federation). The temporary fix you commented works, but I would like a permanent solution. As you said this problem occurs with monorepos

Could you prepare a minimal repo where such issue occurs?

https://github.com/dserra-km/universal-turbo-monorepo/tree/feature/uniwind

This is a minimal showcase with storybook, web and mobile. That's the stack I'm trying to achieve. Both storybook and web work (with module federation). But when I try to make it work for mobile, I get a Maximum call stack error as soon as I add withUniwindConfig to my metro.config (Module federation is no the problem itself). As I said, I need this npmrc configuration due to Module federation, so the only way I've seen so far is the one mentioned in metro.config.

To launch this project, you need to run "pnpm dev" and then "pnpm android" in the mobile/shell path.

As soon as I add this code before the withUniwindConfig for my shell, it works

// Fix for uniwind/metro issue with pnpm symlinks
// https://github.com/uni-stack/uniwind/issues/353
const uniwindPackageJson = fs.realpathSync(
  require.resolve('uniwind/package.json', {
    paths: [__dirname],
  }),
);
const uniwindRoot = path.dirname(uniwindPackageJson);
const uniwindResolveRequest = federatedConfig.resolver?.resolveRequest;

const realpathSafe = (value) => {
  try {
    return fs.realpathSync(value);
  } catch {
    return value;
  }
};

const isUniwindInternal = (originModulePath) => {
  if (!originModulePath) return false;
  const resolvedOrigin = realpathSafe(originModulePath);
  return resolvedOrigin.startsWith(uniwindRoot + path.sep);
};

federatedConfig.resolver = {
  ...federatedConfig.resolver,
  resolveRequest: (context, moduleName, platform) => {
    if (moduleName === 'react-native' && isUniwindInternal(context.originModulePath)) {
      return resolve(context, moduleName, platform);
    }

    if (typeof uniwindResolveRequest === 'function') {
      return uniwindResolveRequest(context, moduleName, platform);
    }

    return resolve(context, moduleName, platform);
  },
};

[Brentlok]

I've spent some time trying to debug it and looks like it's not related to pnpm symlinks at all, and instead it is related to module federation itself, you can remove realpathSync and it will still work.

Uniwind runs resolver from the context - which is from the module federation, and module federation tries to run the uniwind resolver so it causes the loop.

In the fix the resolve function is directly from metro, that's why it's working.
It's almost impossible to fix in the uniwind itself, because using "original" metro resolver may break other setups.
You need to keep workaround for your specific setup