Zoltan Kochan

All the optional dependencies are installed when install runs with the `--force` option. Do you or the bootstrapper install with `--force`?

I wasn't able to reproduce. Can you create a repository on which it reproduces and provide the exact package that you install when it fails.

Sounds good

You can fix it by the [virtual-store-dir-max-length](https://pnpm.io/npmrc#virtual-store-dir-max-length) setting: ``` pnpm config -g set virtual-store-dir-max-length 60 ```

I am OK to add support after npm adds support for it. We already support the `engines.pnpm` field which supports a range, unlike the `packageManager` field, so I don't think...

@GeoffreyBooth I was working on adding packageManager support to pnpm: https://github.com/pnpm/pnpm/pull/8363 @jakebailey mentioned that the packageManager field also supports a blob after a + sign to verify the correctness of...

I have pushed v4 tag.

The issue with this is that `pnpm run` has already a slow startup and this will make it even slower. Unless you come up with some really smart caching mechanics...

It isn't enough to check if the lockfile is up-to-date. You also need to check if node_modules is up to date, which can be done by comparing `node_modules/.pnpm/lock.yaml` to `pnpm-lock.yaml`....

With all the above optimizations that I suggested one expensive operation remains: searching for all the workspace projects in the filesystem. To verify that the lockfile is up to date...