You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
echo'{"dependencies":{"@(-.-)/env":"^0.3.1","zod":"^3.21.4"}}'> package.json
pnpm i # First invocation, installation works fine
pnpm i # Second invocation, installation fails
Expected behavior:
It should work.
Notes:
( and ) characters are valid characters in npm usernames, therefore @(-.-) is a valid npm scope.
This problem does not happen in pnpm v7.x. Maybe this has something to do with the new lockfile format.
Actual behavior:
$ pnpm i (base)
Lockfile is up to date, resolution step is skipped
WARN Broken lockfile: no entry for '/@(-.-)/env/0.3.1(zod@3.21.4)' in pnpm-lock.yaml
ERR_PNPM_ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY The lockfile is broken! Resolution step will be performed to fix it.
ERROR /@(-.-)/env@0.3.1(zod@3.21.4) is an invalid relative dependency path
pnpm: /@(-.-)/env@0.3.1(zod@3.21.4) is an invalid relative dependency path
at Object.parse2 [as parse] (/snapshot/dist/pnpm.cjs)
at nameVerFromPkgSnapshot (/snapshot/dist/pnpm.cjs)
at addPreferredVersionsFromLockfile (/snapshot/dist/pnpm.cjs)
at getPreferredVersionsFromLockfileAndManifests (/snapshot/dist/pnpm.cjs)
at _installInContext (/snapshot/dist/pnpm.cjs)
at async installInContext (/snapshot/dist/pnpm.cjs)
at async _install (/snapshot/dist/pnpm.cjs)
at async mutateModules (/snapshot/dist/pnpm.cjs)
at async install (/snapshot/dist/pnpm.cjs)
at async installDeps (/snapshot/dist/pnpm.cjs)
Additional information:
node -v prints: v18.13.0
Windows, macOS, or Linux?: macOS
The text was updated successfully, but these errors were encountered:
dtinth
changed the title
pnpm: /@(-.-)/env@0.3.1(zod@3.21.4) is an invalid relative dependency path
[regression] pnpm: /@(-.-)/env@0.3.1(zod@3.21.4) is an invalid relative dependency path
Apr 3, 2023
pnpm version:
8.1.0
Code to reproduce the issue:
Expected behavior:
It should work.
Notes:
(
and)
characters are valid characters in npm usernames, therefore@(-.-)
is a valid npm scope.Actual behavior:
Additional information:
node -v
prints: v18.13.0The text was updated successfully, but these errors were encountered: