npm package-lock repair omits a direct package entry #690
|
I can reproduce this with aube 1.13.1 linux-x64 (2026-05-14).
Steps: cd npm-lock-missing-entry
./repro.shThe checked-in
Expected:
Actual:
This came from retesting a larger Expo/React Native app where typecheck then fails with missing |
Replies: 1 comment 2 replies
|
Thanks for the repro. I traced this to npm package-lock writing for dep paths whose peer context has been hashed, e.g. The writer already canonicalized parenthesized peer suffixes like Opened a fix here: #697 Validation on the fixture:
This comment was generated by Codex. |
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_xxxxxxxxxxform. That meant the fixed graph had the direct dep and linked it intonode_modules, but the npm writer skipped the matchingpackages["node_modules/expo-router"]entry because it could not map the hashed dep path back toexpo-router@4.0.22.Opened a fix here: #697
Validation on the fixture:
aube install --fix-lockfile --ignore-scripts --reporter append-onlypackages[""] .dependencies["expo-rou…