You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In our current utilization of the Rush Stack for managing our monorepo, we encounter an issue where all stderr outputs are treated as warnings. This behavior unintentionally interferes with specific caching and building processes, potentially hindering overall efficiency.
Upon investigation, it appears that this behavior is influenced by the ora package.
Describe the solution you'd like
I propose the implementation of a CLI flag or environmental variable that offers selective suppression of CLI logging. This feature would allow users to control the output of stderr messages, mitigating the disruption caused by unnecessary warnings.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In our current utilization of the Rush Stack for managing our monorepo, we encounter an issue where all stderr outputs are treated as warnings. This behavior unintentionally interferes with specific caching and building processes, potentially hindering overall efficiency.
Upon investigation, it appears that this behavior is influenced by the ora package.
Describe the solution you'd like
I propose the implementation of a CLI flag or environmental variable that offers selective suppression of CLI logging. This feature would allow users to control the output of stderr messages, mitigating the disruption caused by unnecessary warnings.
The text was updated successfully, but these errors were encountered: