From 1c9c6af26a39e6c6bf45662767b285d173242504 Mon Sep 17 00:00:00 2001 From: Wes Bos Date: Tue, 17 Dec 2019 09:42:13 -0500 Subject: [PATCH] Quiet it down --- accepted/0018-quiet-it-down.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 accepted/0018-quiet-it-down.md diff --git a/accepted/0018-quiet-it-down.md b/accepted/0018-quiet-it-down.md new file mode 100644 index 000000000..fc462d6ff --- /dev/null +++ b/accepted/0018-quiet-it-down.md @@ -0,0 +1,28 @@ +# npm install output scares people + +## Summary + +`npm install` shows too much low level information which is unhelpful to most developers. + +## Motivation + +There is no way to tell if a `npm install` has worked or not. Many of my students are confused at the output as it looks like something has gone wrong when everything runs just fine. + +## Detailed Explanation + +Just npm install something and look at the output. This was from 100% success: + +![](https://p198.p4.n0.cdn.getcloudapp.com/items/o0uQv6kn/Screen+Shot+2019-12-16+at+3.14.40+PM.png?v=2764c0b9e95ca3ba47a8765e4a13ea1a) + +## Rationale and Alternatives + +Some people have suggested --silent as a good solution, but that will hide good errors as well, no? + +## Implementation + +If everything worked, then don't show a bunch of scary things on the screen. + +## Prior Art + +yarn, pnpm +