`bun run-parallel` and `bun run-sequential` cli commands

[DanielFGray]

What is the problem this feature would solve?

there's often a need to run multiple package.json scripts at a time, either sequentially or in parallel

one sometimes/often sees package.json scripts like "npm run some:task && npm run another:task && npm run yet:another --with-args", and there are also packages like concurrently to run multiple [shell] commands at a time...

What is the feature you are proposing to solve the problem?

two commands (and an alias for each), emulating the api of npm package npm-run-all

• bun run-sequential (alias bun run-s) to run multiple scripts in sequence, allowing one failed script to exit early unless a flag specifies otherwise; the above example could be done with
  bun run-s some:task another:task 'yet:another --with-args'
• bun run-parallel (alias bun run-p) to run multiple scripts in sequence, allowing one failed script to exit all of them (unless a flag specifies otherwise); the same example above would likely make 3 child processes

how stdin is shared with parallel scripts is undefined

What alternatives have you considered?

this could of course be left to the user to install the npm-run-all package, but that package seems to be mostly unmaintained, and sometimes leaves dangling processes [ime]
I think having it as a native cli command in bun would be a fantastic addition to bun

[chocolateboy]

Related: #4402 (comment)

this could of course be left to the user to install the npm-run-all package, but that package seems to be mostly unmaintained

https://github.com/bcomnes/npm-run-all2

[DanielFGray]

https://github.com/bcomnes/npm-run-all2

thanks, I hadn't seen this

since it only supports npm and yarn, it won't execute scripts using bun's task runner and if i understand correctly that also means there's no way to specify whether to use the bun runtime to execute tasks unless the script explicitly uses bun
I dont know if a future update to the package would be able to solve that or not

[ahsath]

https://github.com/bcomnes/npm-run-all2

thanks, I hadn't seen this

since it only supports npm and yarn, it won't execute scripts using bun's task runner and if i understand correctly that also means there's no way to specify whether to use the bun runtime to execute tasks unless the script explicitly uses bun I dont know if a future update to the package would be able to solve that or not

did you have a look at npm-run-all2 --npm-path?

[gkiely]

Alternative syntax: bun --parallel (-p) or bun --concurrent (-c) and bun --sequential (-s)

If this gets added, please consider adding the -r (raw) and -g (group) flags that concurrently supports.

[fawaz-alesayi]

I'm currently using Bun Shell for running multiple commands in parallel.

import { $ } from "bun";

await Promise.all([
    $`<first command>`,
    $`<second command>`
])

I assume you can do the same with sequential commands.

How would this feature be better than using the bun shell and javascript to run multiple commands?

[deadlinecode]

Bun already has a bun --filter '*' dev option so the code to run stuff in parallel is already there
It just needs to made available for running multiple scripts

[sarojregmi200]

Yep, it will be great if this feature gets added to bun. It will reduce one more package and make many lives easier.

[DanielFGray]

as the OP, I just wanted to state that I don't have strong opinions on user-facing api
run-p and run-s seems simple enough but if it's simpler to implement as an extension of the workspace api and provides the same functionality, that's great too

[DerpyDinosaur]

This is working right? This issue could be closed.

[sarojregmi200]

@DerpyDinosaur is it??
I don't see any docs about it. If it is can you tell me how can you use it?

[bnussman-akamai]

bun --filter '*' dev is great for running things in parallel across different workspaces but it would be great to have a command that allows us to run things in parallel in the same workspace so that we don't need npm-run-all or concurrently

I believe pnpm has pnpm run --parallel for this case.

@gkiely makes a great point. I'd really like to have --raw be an option on Bun's --filter and on --parallel if it ever gets added

[0-BSCode]

I'm currently using Bun Shell for running multiple commands in parallel.

import { $ } from "bun";

await Promise.all([
$<first command>,
$<second command>
])
I assume you can do the same with sequential commands.

How would this feature be better than using the bun shell and javascript to run multiple commands?

Hi! I'm following this setup for running spinning up my db, server, and client. This is my script:

// runner.ts
import { $ } from "bun";

const run = async () => {
    await Promise.all([
        $`bun run db:up`,
        $`bun run server:dev`,
        $`bun run client:dev`
    ])
}

These scripts are meant to run my app and so keep running until I hit Ctrl+C on the terminal. Is there a way to perform some action upon terminating the script this way? What I'm trying to do here is spin down my db container since bun run db:up spins up a docker container and I'd like it to be destroyed once I terminate my script.

[mountainash]

@0-BSCode I think you could probably use the Bun.spawn methods and then attach clean-up scripts as needed on the Exit Handlandlers.

[0-BSCode]

@0-BSCode I think you could probably use the Bun.spawn methods and then attach clean-up scripts as needed on the Exit Handlandlers.

Thanks for this! I managed to get it to work with the following set up:

import { $ } from "bun"
const run = async () => {
    Bun.spawn(["bun", "run", "db:up"])
    Bun.spawn(["bun", "run", "server:dev"])
    Bun.spawn(["bun", "run", "client:dev"])

    process.on("SIGINT", async () => {
        console.log("Cleaning up...")
        Bun.spawn(["bun", "run", "db:down"])
        // await $`bun run db:down` will also work
    })

}

run()

For context, bun run db:down is the script I placed in my package.json file to spin down my db container. Leaving this here in case it helps anyone!