Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: Unable to resolve "uuid/v5" in PNPM monorepo #676

Closed
unteifu opened this issue Oct 14, 2023 · 4 comments
Closed

bug: Unable to resolve "uuid/v5" in PNPM monorepo #676

unteifu opened this issue Oct 14, 2023 · 4 comments

Comments

@unteifu
Copy link

unteifu commented Oct 14, 2023

Provide environment information

System:
OS: macOS 14.0
CPU: (12) arm64 Apple M2 Pro
Memory: 114.39 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.5.1 - ~/.nvm/versions/node/v20.5.1/bin/node
npm: 9.8.0 - ~/.nvm/versions/node/v20.5.1/bin/npm
Watchman: 2023.10.09.00 - /opt/homebrew/bin/watchman

Describe the bug

Whenever I start the dev in expo go i get the following error:
Unable to resolve "uuid/v5" from "../../node_modules/expo/build/environment/getInstallationIdAsync.js"

I've seen some conversation about this issue but it was a long time ago and was apparently fixed so I'm kinda at a lost

Link to reproduction

#165

To reproduce

In feat pull

Additional information

No response

@unteifu
Copy link
Author

unteifu commented Oct 14, 2023

setting config.resolver.disableHierarchicalLookup in the metro.config.js fixes things but that's not the recommended way to have things in a monorepo

@by14
Copy link

by14 commented Oct 20, 2023

Same problem - any fixes besides commenting out config.resolver.disableHierarchicalLookup?

@juliusmarminge
Copy link
Member

setting config.resolver.disableHierarchicalLookup in the metro.config.js fixes things but that's not the recommended way to have things in a monorepo

It is actually the recommended way, but I've had mixed results with it in the past... https://docs.expo.dev/guides/monorepos/#modify-the-metro-config

@juliusmarminge
Copy link
Member

Hopefully it's resolved for everybody now with Expo 50 introduced in #795

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants