berry: [Bug] `yarn workspaces foreach exec` fails

@DerekZiemba You’re using Yarn Classic (v1), while yarn workpaces foreach is a Yarn 2 feature. You can consult the installation guide to install Yarn 2. If it still doesn’t work, you should probably open another issue, as it’s unlikely it would be related to this one.

Yeah, but yarn workspaces foreach run depcheck won’t do a thing unless there are depcheck scripts in all workspaces. Is that expected behaviour?

It will skip over scripts that don’t declare a script of this name, yes. However it probably should execute it too if there’s a binary of the specified name, so if it doesn’t do so already I’d see that as a bug.

run as alias to yarn run

That’s funny, I never considered it would work with exec. I initially made it this way because it turns out there’s no real portable way to run a script regardless of the package manager (each time you need to explicitly specify npm / yarn / pnpm, …). I haven’t advocated it to other package managers though, so it’s not portable either (yet).

yarn exec has been implemented, but it hasn’t been released yet. You can do yarn set version from sources to build and use the version from master, which includes yarn exec.

Edit: And yes, it’s supported by yarn workspaces foreach, I can confirm that yarn workspaces foreach exec ls works.