Khải

@MoazAlkharfan Try changing `catalogs` (plural) in your `pnpm-workspace.yaml` into `catalog` (singular)

The lockfile will always include optional dependencies regardless of whether pnpm installs them. You should run `ls node_modules/.pnpm/cpu-features*` to verify whether pnpm has actually installed it.

Hello again, @EdwardDrapkin. This is a non-issue and should be closed, but I have left this issue open to wait for your response. Have you received my message?

> PNPM definitely installs it Please do a clean install again and run `ls node_modules/.pnpm/cpu-features*` then tell me the output. The command I use was `pnpm install --no-optional ssh2 &&...

The token already presents in `specifier`. Why do you need it in `version` as well? Does it cause `pnpm install` to stop working?

I see. So this bug can be fixed either by re-adding auth token to `version` or make pnpm fetch infer auth token from the specifier.

@baixiaoyu2997 In the meantime, you need to provide your vercel builder a private SSH key that has access to the private repositories.

@zkochan > Probably this started happening after this was merged: #6806 This PR was later [reverted](https://github.com/pnpm/pnpm/issues/6805#issuecomment-1639992599) and replaced by https://github.com/pnpm/pnpm/pull/6832

The writing of packument only happens when there's no lockfile, right? In which case, I think network request alone overshadows what little CPU time parsing and stringifiying cost. Of course,...

I always thought "packument" was a weird term. Do you make use of the [packument](https://www.npmjs.com/package/packument) package, @zkochan? I personally prefer "metadata".