Contribution

• I'd be willing to implement this feature (contributing guide)

Describe the user story

As a project maintainer, I want to run a dry run of the install command so that I can run it locally in a pre-commit hook, eliminating a path where developers have failing builds because of outdated lockfiles and other common errors.

If I could do a dry run with success and failure exit codes, I could warn developers pre-commit and prepush that their packages were out of date.

Describe the solution you'd like

I would like to implement the dry run option for the install command, as was proposed but closed here:

#406

I think this qualifies as a mainstream usecase.

Describe the drawbacks of your solution

I don't think there are drawbacks here.

Describe alternatives you've considered

I've looked into post install hooks (not really supported) and other integrity checks, but the thing I really want is to run the tool in a dry run mode since what I am checking for is if pnpm will run without errors, and other solutions are proxies.

This will eliminate a whole class of developer issues, which makes it worthwhile in my view.