workspace package folders and node_modules folders are not created by `pnpm install` and silently fail about pnpm HOT 3 OPEN

I think pnpm install --frozen-lockfile should fail in this case.

We have a special command for your scenario: pnpm fetch. Looks like this command fails currently in this case, it should be fixed.

from pnpm.

@zkochan --frozen-lockfile failing sounds like a great approach! Thank you for considering this!

We have a special command for your scenario: pnpm fetch. Looks like this command fails currently in this case, it should be fixed.

I actually do use pnpm fetch in my dockerfile, but left it out of the repro repo as it didn't seem critical to the bug. As far as I can tell, pnpm fetch does fetch something but it's not clear to me if it fetches everything in the lockfile or just root level dependencies in this specific case of the folders not being present. My expectation is that it would fetch everything in the lockfile, if you're also saying that pnpm fetch would have a bug in this case.

from pnpm.

I would expect any workspace packages listed in the pnpm-workspace.yaml and pnpm-lock.yaml to have their node_modules present, even if the folders aren't present.

One other note on this: the reason I mentioned this as an expectation is that for a large monorepo, even when pnpm fetch is cached in docker, the pnpm install step still takes time to link everything. So I was hoping to even cache that step in docker as well given that dependencies don't change as frequently as source code.

But I understand if changing the behavior of --frozen-lockfile to create directories is considered unexpected by most!

from pnpm.