-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[BUG] npm run-script --silent now broken completely #2023
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
Comments
CliffS
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
labels
Oct 23, 2020
We are facing the same issue. In Jenkins we use |
macno
added a commit
to macno/cli
that referenced
this issue
Oct 30, 2020
@CliffS there's a typo in the title: |
CliffS
changed the title
[BUG] rpm run-script --silent now broken completely
[BUG] npm run-script --silent now broken completely
Oct 30, 2020
ruyadorno
pushed a commit
that referenced
this issue
Oct 30, 2020
Released npm 7.0.7 that fixes it:
I think we can close this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
Note: Issue #1958 refers to
--silent
suppressing all output.Current Behavior:
npm run --silent script
now outputs everything, eg:In other words, the
--silent
flag is doing nothing.Expected Behavior:
Steps To Reproduce:
See above.
Environment:
The text was updated successfully, but these errors were encountered: