Pelle Wessman

I have released [installed-check 9.0.0](https://github.com/voxpelli/node-installed-check/releases/tag/v9.0.0) which includes workspace support, possibly unblocking this

Thanks for letting me know about`pnpm-workspace.yaml`, I'll add support for it :+1: https://github.com/voxpelli/read-workspaces/issues/2 I wouldn't say that its an issue that some packages support a wider version than you do...

Released version [`9.1.0`](https://github.com/voxpelli/node-installed-check/releases/tag/v9.1.0) which has preliminary support for resolving pnpm workspaces + adds a new output in verbose mode that lists all successful and unsuccessful workspaces. Looks like this: ![Skärmavbild...

@colinrotherham It's because you use `**` in `pnpm-workspace.yaml` rather than `*`, would it work do go with eg. `packages/*` instead of `packages/**`? https://github.com/webdriverio/webdriverio/blob/a46cea223eadc22d3c68338dd58e20454c206917/pnpm-workspace.yaml#L2-L5 It probably occurs here because I bolted...

I released a fix for symlinks 30 minutes ago, along with some other pnpm quality of life improvements: https://github.com/voxpelli/node-installed-check/releases/tag/v9.1.1 I will download your repository and do some more checking

After some digging I found https://github.com/pnpm/pnpm/issues/3398 and by adapting the suggestion in https://github.com/pnpm/pnpm/issues/3398#issuecomment-835277787 I could conclude that pnpm is also resolving the `/build/` workspaces: ```sh ❯ pnpm ls -r --depth...

If you update to `[email protected]` then you can now do: ```sh pnpm exec installed-check --engine-check --ignore-dev --workspace-ignore='**/build/**' ``` It makes the repo work after `pnpm run setup`. Thanks for helping...

I added a `--fix` in `[email protected]` as it makes more sense now with big monorepos like this. So you can now at least fix these easily 🙂

Thanks for stepping in and merging @JoshuaKGoldberg 🙏 🙂

This one needs to be updated now, but preferably it would wait until #5042 is merged