Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tailwind-cli casually emits to stderr #13680

Closed
datner opened this issue May 13, 2024 · 2 comments
Closed

tailwind-cli casually emits to stderr #13680

datner opened this issue May 13, 2024 · 2 comments

Comments

@datner
Copy link

datner commented May 13, 2024

when using a tool like process-compose and others such executioners this causes the process to immediately exit even if the --watch option is passed. This should not be emitted to the error channel to begin with, it denotes a success

@thecrypticace
Copy link
Contributor

Hi! This is intentional and follows the standard conventions around how CLI tools are built.

This should not be emitted to the error channel to begin with, it denotes a success

This is common misconception. Per the POSIX standard stderr is not strictly for errors. It's meant to be used for any diagnostic output. This includes things like human readable output, user-interactive prompts (several shells do this), information messages, warnings, errors, progress reporting (e.g. this is what curl does). Generally stdout should be used for things you'd want to pipe to either a file or another program.

@datner
Copy link
Author

datner commented May 16, 2024

Thanks for the explaination

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants