feat(cli/unstable): support stderr on spinner

[andrewthauer]

Related to #5495

Adds support to the @std/cli/unstable_spinner to write to stderr instead of the default stdout.

The current Spinner is unusable when piping to another command (e.g. deno_cli | less for paging). and will cause garbled data to the pipe/console. Using stderr is the standard approach for informational text since by default it is not passed along to the piped commands stdin.

NOTE: I personally would be happy to make this the default. I'm curious if folks would be open to this considering it's currently unstable.

An alternative could be to check if the terminal is interactive or not and change the default based on this.

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 96.34%. Comparing base (5af091b) to head (364e4a3).

Files with missing lines	Patch %	Lines
cli/unstable_spinner.ts	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6350      +/-   ##
==========================================
+ Coverage   96.33%   96.34%   +0.01%     
==========================================
  Files         552      552              
  Lines       41938    41940       +2     
  Branches     6354     6355       +1     
==========================================
+ Hits        40399    40406       +7     
+ Misses       1499     1494       -5     
  Partials       40       40              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kt3k]

Looks reasonable addition to me.

Can you also add an example of passing Deno.stderr in Spinner class jsdoc?

[andrewthauer]

@kt3k - Updated example. I'm curious if you have an opinions or there is a standard name to use for the stream option?

Also any thoughts on making this the default vs stdout? From my perspective there aren't many or any downsides and only upsides to having this as the default. I've noticed other libraries already conform to the pattern of using stderr for informational things (e.g. dax, cliffy).

[kt3k]

I'm curious if you have an opinions or there is a standard name to use for the stream option?

I don't think there's standard name for it, but how about output as it doesn't accept arbitrary stream?

Also any thoughts on making this the default vs stdout? From my perspective there aren't many or any downsides and only upsides to having this as the default. I've noticed other libraries already conform to the pattern of using stderr for informational things (e.g. dax, cliffy).

That sounds reasonable to me. Let's continue on that change after this one.