pnpm crashes because of bad non-null assertion at newLockfile.packages!

[jedwards1211]

Clearly non-null assertions are an antipattern...

pnpm version: 7.14.0

When I try to install one of my private packages I get a null pointer error on newLockfile.packages here:

pnpm/packages/resolve-dependencies/src/index.ts

Line 335 in 11669e6

if (requiresBuild && newLockfile.packages![depPath]) {

Code to reproduce the issue:

I'm afraid I haven't gotten it down to an easy repro as this only happens when I try to install one of my private packages on an AWS instance so far.

[zkochan]

I guess we can easily fix this, but it would be interesting to see in what case it is null. I can't find any scenario when that would happen. Unless someone creates an afterAllResolved hook in .pnpmfile.cjs and removes the field from the lockfile.

[jedwards1211]

If it helps, I was trying to sudo pnpm i -g <tarball url> on an AWS EC2 Instance. I tried at one point with a tarball made by npm with bundleDependencies: true, but also one without bundling dependencies.