-
-
Notifications
You must be signed in to change notification settings - Fork 607
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
Add notification about npm output #848
Comments
Is there any silent mode or piping stderr or anything that we could incorporate into the command? |
Yeah -- but that would hide stuff to help them resolve their configuration / local system. |
We can ask npm |
Maybe fix the vulnerabilities? |
|
And they're usually not vulnerabilities in the sense that there is an attack surface/vector. |
npm
outputs very scary looking "vulnerability" messaging, multiple times, all the way down the dependency tree, when there is a CVE for such dependency. About 100% of the time, these warnings are not applicable to the use-case of this track and can safely be ignored.Add a message about this in the instructions to avert issues like exercism/exercism#5212.
The text was updated successfully, but these errors were encountered: