René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"npm loglevel should be left as default","articleBody":"There are a long list of arguments why docker shouldn't be changing npm's default and a lot of vocal support for removing the verbose setting. Now that it's been over a year since this was [last discussed](https://github.com/nodejs/docker-node/issues/57), I would like to reopen the discussion to consider returning to npm's default.\r\n\r\n- conflicting with npm's own default setting is jarring and violates principle of least surprise\r\n- `warn` _already_ prints (typically) enough info during a failure case. the scenarios where `info` is actually necessary to debug a failure are vanishingly slim. indeed, failures themselves are the exception, so `info` is necessary in a fraction of a fraction of cases\r\n- the env var can't be overridden with .npmrc or `npm config set` because env vars take precedence. thus the only way to get _back_ to npm's default is to set our own env var\r\n-the vast majority of people are now forced to manually undo a setting for the tiny percentage that want it to be different than npm's default\r\n\r\nAnd most importantly, contrary to the documented rationale for this setting:\r\n\r\n- it's [possible](https://github.com/nodejs/docker-node/issues/57#issuecomment-268799511) to get the full debug log during a failure _without_ being overly verbose to `STDOUT`\r\n\r\n\r\nAt the _very_ least, this setting should not be set via environment variable, but rather via the builtin config file. `$PREFIX/etc/npmrc` is specifically for distributions to customize defaults to their liking. Using this would allow users to force it _back_ to npm's default using either user or project `.npmrc`, instead of forcing users to override using env var or cli flag.","author":{"url":"https://github.com/jasonkarns","@type":"Person","name":"jasonkarns"},"datePublished":"2017-09-18T15:12:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/528/docker-node/issues/528"}