withClerkIOS: ClerkViewFactory.swift not found in pnpm workspaces nested 2+ levels deep

[davidtiede]

Bug report

Description

The withClerkIOS config plugin fails to find ClerkViewFactory.swift when the Expo app is nested 2+ levels deep in a pnpm workspace (e.g. apps/mobile/).

possiblePaths only checks one level up

In app.plugin.js, the possiblePaths array resolves paths relative to config.modRequest.projectRoot:

• ./node_modules/@clerk/expo/ios/ClerkViewFactory.swift
• ../node_modules/@clerk/expo/ios/ClerkViewFactory.swift
• ../packages/expo/ios/ClerkViewFactory.swift

In a standard pnpm workspace monorepo like:

monorepo/
├── node_modules/@clerk/expo/   ← package hoisted here
├── apps/
│   └── mobile/                 ← projectRoot is here
├── pnpm-workspace.yaml
└── package.json

The package lives at ../../node_modules/@clerk/expo/ relative to projectRoot, which none of the possiblePaths entries cover.

Suggested fix

Replace the hardcoded paths with require.resolve to let Node's module resolution handle arbitrary nesting:

const swiftFile = require.resolve('@clerk/expo/ios/ClerkViewFactory.swift');

Or, if you want to keep the possiblePaths approach, walk up the directory tree instead of checking only one level:

let dir = config.modRequest.projectRoot;
while (dir !== path.dirname(dir)) {
  possiblePaths.push(
    path.join(dir, 'node_modules', '@clerk', 'expo', 'ios', 'ClerkViewFactory.swift')
  );
  dir = path.dirname(dir);
}

Workaround

We're using pnpm patch @clerk/expo to add the ../../node_modules/ path manually.

Environment

• @clerk/expo: 3.1.2
• pnpm workspaces with app at apps/mobile/
• Expo SDK 55

[chriscanin]

Hello @davidtiede , thank you for the bug report. We have a fix in queued up to get merged in.
Please check it out here if you have the time. #8111

I will close this issue when the fix has been merged in.

Hope your week is going well!

[chriscanin]

Hi @davidtiede , we have released a new version of @clerk/expo that should resolve this issue. If you pull the latest version, you should be able to create the build.

We appreciate your patience and time in pointing out this issue.

[davidtiede]

Nice, I was actually just working on this with the 3.1.5 canary build so I'll grab the latest and give it a try. Thanks for the quick turn around! I'll keep you posted.