Perform additional validation for undefined
dependency ranges after readPackage()
hook
#5517
Labels
undefined
dependency ranges after readPackage()
hook
#5517
// This is probably somewhere between a bug and a feature request
pnpm version:
7.13.4
,7.13.5
Code to reproduce the issue:
The simplest repro would be a
readPackage()
hook that accidentally sets a dependency range toundefined
:See https://github.com/walkerburgin/pnpm7-readpackage-delete-repro for a standalone repro that's representative of how we actually encountered this while upgrading our large monorepo from pnpm v6 to pnpm v7.
Expected behavior:
In a perfect world, PNPM would either ignores any dependency with an
undefined
range, or fail with a more explicit error.Actual behavior:
PNPM crashes with a stack trace like this:
This is maybe tangentially related to #4415 (and to a lesser extent #5493).
Additional information:
node -v
prints:v16.17.1
The text was updated successfully, but these errors were encountered: