Skip to content
Discussion options

You must be logged in to vote

Thanks for the repro. I traced this to npm package-lock writing for dep paths whose peer context has been hashed, e.g. expo-router@4.0.22_94c00fd028.

The writer already canonicalized parenthesized peer suffixes like pkg@1.0.0(peer@1.0.0), but it did not canonicalize the hashed _xxxxxxxxxx form. That meant the fixed graph had the direct dep and linked it into node_modules, but the npm writer skipped the matching packages["node_modules/expo-router"] entry because it could not map the hashed dep path back to expo-router@4.0.22.

Opened a fix here: #697

Validation on the fixture:

  • aube install --fix-lockfile --ignore-scripts --reporter append-only
  • confirmed packages[""] .dependencies["expo-rou…

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@mwolson
Comment options

@mwolson
Comment options

Answer selected by mwolson
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants