tomoemon

Thank you for detailed explanation! I understand what you want to resolve. The first thing I felt was that this writing style is a bit redundant. ```typescript let branch =...

Looks great! Thank you for your understanding. There are a few things I would like to confirm. - Are text() and arrayBuffer() supposed to return just the standard output? (I...

> (I guess that's also what you meant when you said (I think that's fine) ?) Sorry for the vague wording. I agree with you. > It's not really straightforward...

> That's an interesting idea (Response & { stderr: Response }), but won't this be disruptive to users? Should the command status be passed to stderr as well? What about:...

> I couldn't find the time to add a custom Error subclass with command status info (like zx do) Even though I have read `zx` code, I couldn't find the...

Awesome! The example you provided looks close to ideal interface. But I haven't understood yet how you are going to implement error handling. A ```typescript let result: Response = await...

> The idea is that it depends on where the await is: Understood, thank you! I like this rule, so simple. > Anyway, Response might not be a good idea...

Perfect! I was surprised at how quickly you implemented it! I've tried `dev` code a few and it is very comfortable to use. I'll try to read details later!

(This might be another issue) Common use-cases for me ## reading line one by one Opening file (or Piping another command) as stream and reading line by line are common...

Understood! So If I want to provide utility functions for me and other bazx users, I can just publish it in my own repository myself.