Hacker News Reader

Comment by rattray | Hacker News Reader

Sorry if I'm being dense/lazy, but can you give an example of what this looks like:

> Bun shell replaced the need for something like “concurrently”.

"Concurrently" is a nodejs library for running more than one task at once, it's necessary if you want to build Typescript and Tailwind with one call to `npm run build`, for example.

It's kind of a PITA to use, and just calling a Bun script is better.

Right; what does it look like with bun?

I'm not on my machine where the project is, but it looks something like this:

    await Promise.all([
      $`bun watch:server`,
      $`bun watch:tailwind`,
      $`bun watch:client`,
    ]);

How's that different from:

  await Promise.all([
    child_process.exec(...),
    child_process.exec(...),
    child_process.exec(...),
  ]);

Syntax might be off but you get the idea ...

It's probably not different. It works the way I want it to / expect it to in Bun, where with Node's process.* functions, I always run into a footgun before I get it working properly.

Okay, I get what you mean.

Ah, interesting! Thanks!

Reply on news.ycombinator.com