Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SDK45: Unable to resolve module uuid/v5 in expo go

See original GitHub issue

Summary

Initializing a new sdk45 beta project and using “uuid” in expo go throws the following error

iOS Bundling failed 1021ms
Unable to resolve module uuid/v5 from {file paths}/node_modules\expo\build\environment\getInstallationIdAsync.js: uuid/v5 could not be found within the project or in these directories:
  node_modules\expo\node_modules
  node_modules
  1 | import * as Application from 'expo-application';
> 2 | import uuidv5 from 'uuid/v5';
    |                     ^
  3 | let installationId;
  4 | const UUID_NAMESPACE = '29cc8a0d-747c-5f85-9ff9-f2f16636d963'; // uuidv5(0, "expo")
  5 | export default async function getInstallationIdAsync() {

Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

iOS

SDK Version (managed workflow only)

SDK45

Environment

  expo-env-info 1.0.3 environment info:
    System:
      OS: Windows 10 10.0.19044
    Binaries:
      Node: 16.14.0 - C:\Program Files\nodejs\node.EXE
      Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
      npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD
    npmPackages:
      expo: ~45.0.0-beta.4 => 45.0.0-beta.8
      react: 17.0.2 => 17.0.2
      react-dom: 17.0.2 => 17.0.2
      react-native: 0.68.1 => 0.68.1
      react-native-web: 0.17.1 => 0.17.1
    Expo Workflow: managed

Reproducible demo

https://github.com/ramiel1999/expo-sdk45-uuid

Issue Analytics

State:
Created a year ago
Reactions:2
Comments:6 (2 by maintainers)

Top GitHub Comments

5reactions

brentvatnecommented, Apr 28, 2022

fixed in expo@45.0.0-beta.9

4reactions

davidzech27commented, Nov 30, 2022

I discovered that by removing another package in the monorepo which had uuid as a dependency, the issue went away. However, removing uuid in that package wasn’t an option. The only thing that has solved the issue has been setting config.resolver.disableHierarchicalLookup to false in metro.config.js, going against what is recommended in the docs. Still looking for a better solution, if anyone has one.