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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] Force colors where possible #345

Closed
brandonbloom opened this issue Sep 21, 2021 · 1 comment · Fixed by #365
Closed

[FEATURE] Force colors where possible #345

brandonbloom opened this issue Sep 21, 2021 · 1 comment · Fixed by #365
Labels
feature request Community feature request

Comments

@brandonbloom
Copy link
Member

A key motivation for #344 (PTY support) is to convince programs to print colors in logs. Full PTY support is a tall order, so until then, maybe we should do some buildpack-like magic to determine which environment variables to set to encourage programs to override their PTY detection.

For example, FORCE_COLOR=1 for the npm chalk package used by next.js. See vercel/next.js#11836 (comment)
@brandonbloom brandonbloom added feature request Community feature request needs triage Incoming request that needs to be triaged and prioritized and removed needs triage Incoming request that needs to be triaged and prioritized labels Sep 21, 2021
@brandonbloom
Copy link
Member Author

cc @finnigantime

brandonbloom added a commit that referenced this issue Sep 27, 2021
@brandonbloom
FORCE_COLOR & fix default environment for .env
bd7f2f8 
Closes #345
@brandonbloom brandonbloom mentioned this issue Sep 27, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Community feature request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

FORCE_COLOR & fix default environment for .env deref/exo
1 participant
@brandonbloom