prefix "yarn workspaces run" (v1.10.0) output with package names

[donaldpipowitch]

Do you want to request a feature or report a bug?

feature

What is the current behavior?

$ yarn workspaces run build
yarn workspaces v1.10.0
yarn run v1.10.0
$ tsc -p src
✨  Done in 1.49s.
yarn run v1.10.0
$ tsc -p src
✨  Done in 1.21s.
yarn run v1.10.0
$ tsc -p src
✨  Done in 1.41s.
✨  Done in 5.26s.

What is the expected behavior?

Similar to wsrun --serial:

$ yarn build
yarn run v1.10.0
$ wsrun build --serial
package-a
$ tsc -p src
package-b
$ tsc -p src
package-c
$ tsc -p src
✨  Done in 4.86s.

(Note, in the terminal package-a/b/c are also written bold to make the log even nicer to read.)

Please mention your node.js, yarn and operating system version.

• Node 8 LTS
• yarn v1.10.0
• macOS

[alexindigo]

Another option would be similar to how Jenkins does it:

$ yarn workspaces run build
yarn workspaces v1.10.0
[package-a] yarn run v1.10.0
[package-a] $ tsc -p src
[package-a] ✨  Done in 1.49s.
[package-b] yarn run v1.10.0
[package-b] $ tsc -p src
[package-b] ✨  Done in 1.21s.
[package-c] yarn run v1.10.0
[package-c] $ tsc -p src
[package-c] ✨  Done in 1.41s.
✨  Done in 5.26s.

Also this format will be more useful, when yarn allow running workspace scripts in parallel (wink, wink, it was in the proposal).

[ianstormtaylor]

I think borrowing from Lerna with its color-coding would be nice:

[zkochan]

We have a similar discussion in pnpm: pnpm/pnpm#1440

[peterlebrun]

Hi - I believe I have addressed this in the following PR: #6932

Thanks!

[grrowl]

If you're using Yarn Berry, the command is yarn workspaces foreach and pass the --verbose argument to prefix the output with the package's name