Should pnpm i --force recreate the lock file?

[jimmythomson]

I'm using a .pnpmfile.cjs file to switch out some dependencies based on an environment variable. When I change the environment variable, I want to be able to recreate the lock file with references to the updated dependencies (as controlled by the .pnpmfile.cjs file). I thought that pnpm i --force would do the job, but the --force flag doesn't appear to force anything to happen using pnpm 10.0.0. Is there another way to force the recreation of the lock file, short of deleting the node_modules folder or altering a package.json file?

Thanks.

[zkochan]

Try pnpm install --resolution-only but then you will need to run pnpm install

[zkochan]

We store the hash of the .pnpmfile.cjs in the lockfile. Like here:

pnpm/pnpm-lock.yaml

Line 673 in 31fdf35

pnpmfileChecksum: sha256-mx8+uzkaD2WO2V3h9zTchFZZX3QdTTMrkVNvy8svgCY=

If the content changes, the hash changes and pnpm does full resolution. So, I am not sure why it didn't work. Did the hash change in the lockfile?

[jimmythomson]

The value of the pnpmfileChecksum doesn't change after updating the .pnpmfile.cjs file.

[zkochan]

Did you modify .pnpmfile.cjs or another file required by .pnpmfile.cjs? The hash is calculated solely from the raw content of .pnpmfile.cjs. If so, there must be some bug.

[jimmythomson]

I edited the .pnpmfile.cjs file directly.

[jimmythomson]

To work around this, I'm going to upgrade to version 10.2.1 and set the optimistic-repeat-install to false.