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

fix(ng-dev): improve spinner experience when executed in a CI environment #2426

Closed

Conversation

josephperrott
Copy link
Member

Improve the spinner experience in a CI environment so that it does not show the same message repeatedly, but also continues to show output to prevent CI environments from treating the execution as inactive.

…ment

Improve the spinner experience in a CI environment so that it does not show the same message repeatedly, but also continues to show output to
prevent CI environments from treating the execution as inactive.
@josephperrott josephperrott added the action: merge The PR is ready for merge by the caretaker label Nov 7, 2024

/** Whether execution is in a CI environment. */
const IS_CI = process.env['CI'];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this point in time we keep making the spinner more complicated. Should we consider just using a library here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is still markedly less complicated than a library has, we can if you would like, but I do personally like the total control we have in this case. But if you feel strongly I am happy to look into options for us.

Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pretty cool. LGTM.

I don't feel strongly about the npm library, and I think the code is clean, so LGTM.

@josephperrott
Copy link
Member Author

This PR was merged into the repository by commit 11967c8.

The changes were merged into the following branches: main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants