Cannot find module issues persist

[IrvingArmenta]

Requirements: This library requires Mapbox Maps SDK v11 and React Native 0.79+ with New Architecture (Fabric/TurboModules).

For sponsors-only support and resources: https://github.com/rnmapbox/maps/wiki/SponsorsRepo
Become a sponsor for special support: https://github.com/sponsors/rnmapbox

---

Environment

• Dev OS: Windows 11 (PowerShell)
• @rnmapbox/maps version: 10.3.5
• React Native version: Expo SDK 57 (React Native 0.73+)
• Expo CLI version: 57.0.18
• pnpm version: 11.23.0

Steps to reproduce

pnpx create-expo-app sample
cd sample

# Install rnmapbox/maps
pnpm expo install @rnmapbox/maps@latest

# Add plugin
# app.json:
# {
#   "expo": {
#     "plugins": ["@rnmapbox/maps"]
#   }
# }

pnpm expo prebuild --clean
pnpm expo run:android

Actual behavior

1. Expo cannot resolve the config plugin in app.json

In VS Code, hovering over "@rnmapbox/maps" inside "plugins" shows:
Cannot find module '@rnmapbox/maps'

2. Expo prebuild fails with module resolution errors

During the Expo config plugin phase, the build fails with:
Cannot find module '@rnmapbox/maps'

Expected Behavior

Expo’s config plugin should be discoverable in app.json, and Expo should load:
lib/module/Mapbox.js

[Hot-IOce]

This looks like pnpm's module layout rather than anything in @rnmapbox/maps — the giveaway is that it fails identically in the VS Code plugin resolution and in expo prebuild, on a package that is definitely installed.

By default pnpm uses the isolated node-linker: real packages live in node_modules/.pnpm and only your direct dependencies get symlinked at the top level. Expo's config-plugin resolution require.resolves the plugin from the project root and follows the realpath into the store, where the package's own dependency graph isn't resolvable — so it reports the plugin as missing even though it's installed.

Expo's recommended setup for pnpm is the hoisted linker. Create .npmrc next to package.json:

node-linker=hoisted
then reinstall from clean, because the existing tree is already in the wrong shape:

rm -rf node_modules pnpm-lock.yaml
pnpm install
pnpm expo prebuild --clean
(PowerShell: Remove-Item -Recurse -Force node_modules, pnpm-lock.yaml)

One extra thing specific to Windows 11: pnpm's default layout needs symlinks, and Windows only allows creating them with Developer Mode on or from an elevated shell. If that's off, pnpm silently produces a tree that looks right and doesn't resolve. Worth enabling Developer Mode before the reinstall — Settings → System → For developers.

Same failure shows up with other config plugins under pnpm — there are matching open reports against react-native-maps and react-native-datetimepicker — so it isn't Mapbox-specific, which hopefully saves you chasing it in the wrong repo.

If it still fails after the hoisted reinstall, post the output of pnpm why @rnmapbox/maps and whether node_modules/@rnmapbox/maps is a real directory or a symlink — that'll separate a resolution problem from an install problem.