Closed yus-ham closed 6 months ago
I just realized that that npm-run-all
has last been published 5 years ago 😅 But I use it all the time!
concurrently
works on Bun apparently so at least we have an alternative.
concurrently
works on Bun apparently so at least we have an alternative.
I dont know about concurently
.
Mainly I use run-p
for spawning php dev server. But finally, instead I replaced run-p with my own vite plugin using Bun.spawn() to start php-cgi
Newest error as of Bun v1.0.7.
❯ bun --bun run all
$ run-p echo-hello echo-world
ERROR: Invalid stdio option "[object ReadStream]"
error: script "all" exited with code 1 (SIGHUP)
to implement stdio option "[object ReadStream]"
, edit src/js/node/child_process.js, this is a implementation of the node api using Bun.spawn. we do not handle node streams as stdio inputs. some refactoring in the code is needed to allow nonstring stdio options, but this should be pretty easy to implement. idk if that's the only thing blocking it, but if so this would be a good "good first issue" tag.
Is it possible to create a similar syntax as npm-run-all
that allows for similar functionality. Example:
bun run-all -s lint:{foo,bar} -p serve:dev -p open:browser
## Which is the same as
bun run lint:foo
bun run lint bar
bun run server:dev &
bun run open:browser
Why is this issue closed? I don't think bun is working with
(Sorry for the false claim. It works.)npm-run-all
as of right now.
@alexkuang0 if you have a repo or script that reproduces the issue on the latest version of Bun we'd be happy to get it fixed on a new issue
@nektro Sorry I want to make this right. It's now working for me. But I did encountered once when Bun didn't work with npm-run-all
. I forgot how to reproduce it and I'm not even sure if Bun was the issue there. I have updated my previous comment to be false claim.
What version of Bun is running?
0.8.2+a846852818278641cf33413ce784adf2fc0e2e52
What platform is your computer?
Linux 5.15.0-67-generic x86_64 x86_64 - ubuntu 22.04
What steps can reproduce the bug?
make a project with only has
npm-run-all
in depsRun
bun install && bun --bun run all
What is the expected behavior?
What do you see instead?
Additional information
No response