Add process.stdin, process.stdout and process.stderr

[Perodactyl]

What is the problem this feature will solve?

It will allow more compatibility with node.js programs and make it easy(or maybe even stop it from being impossible) to receive user input.

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

Adding More support for process.stdin and process.stdout (specifically, process.stdin.on("data", ()=>{...} and process.stdout.write("..."))

What alternatives have you considered?

I have no fix for stdin so far, stdout I could maybe store all my lines in a string and log them whenever (would still always end in a newline, but would fix writing chars without an automatic newline)

[franciscop]

I'd be happy to provide a polyfill for process.stdin and process.stdout, but I'm blocked (which in turns blocks me on #311 (comment)) in trying to get process.stdout behave like a WritableStream at all see original:

console.log(Bun.stdin.stream(), Bun.stdout.stream());
// ReadableStream { } ReadableStream { }

I have tried many things in JS-land to no avail, so would love some input about how to make Bun.stdout behave somehow like a WritableStream instead of a ReadableStream, or how to write data to it in any way. Unfortunately the Zig source code is illegible for me, so I've been trying things in JS-land only.

[samfundev]

@franciscop You need to use Bun.write and Bun.stdout together:

// log a file to stdout
await Bun.write(Bun.stdout, Bun.file("input.txt"));

[samccone]

Shimming my global process.stderr does the trick in my case: (your mileage might vary)

if (typeof process.stderr == "undefined") {
  process.stderr = Bun.stderr;
}

[samfundev]

I believe this issue can be closed with the release of v0.3.0.

[Electroid]

Yep! This is now supported in Bun v0.3.0 🎉