-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
reduce effect of npm silent loglevel #2706
Conversation
@bkucera Merge conflict |
I understand the changes made to the I'm pretty sure that was the point of using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment
@brian-mann However, I think we could get away with just the
|
Hey @bkucera, could you address the merge conflict here and follow up with any leftover work to merge this in or close if stale. Thanks! |
fixed merge conflict, I think this should be merged. The comment that @brian-mann had was that with these changes we go from 0 lines of stdout with I think that's a fine amount of stdout for |
Test summaryRun details
View run in Cypress Dashboard ➡️ This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
Closing due to inactivity. Please reopen or open a new pull request to address the changes necessary in this PR. |
fix #2705
changes:
npm i cypress --silent
has Listr verbose renderer: (previously there were no console logs)but, we could change this to use default renderer
cypress verify
ignores--silent
logger.log()
are no longer silenced, only calls tologger.info
, socypress version
,cypress cache list
, etc will not be silenced bynpm_config_loglevel