src: make the npm source comply with `standard`

This is a huge set of mostly mechanical changes. Going forward, all
changes to the npm source base are expected to comply with `standard`,
and it's been integrated into the test suite to enforce that. There are
a few notes below about specific classes of changes that need to be
handled specially for npm's code base.

standard: "Expected error to be handled."

`standard` only expects errors spelled "err" to be handled.
`npm-registry-mock` never actually invokes its callback with an error,
so in some cases I just changed it to be spelled "er" and called it
good.

standard: "Expected a "break" statement before 'case'."

This behavior is actually on purpose, and I don't feel like rewriting
the affected code right now (or, you know, ever). So I added code
comments disabling the checks in the three applicable changes.

standard: "x is a function."

Rebinding functions created via declarations (as opposed to expressions)
is a no-no?

PR-URL: https://github.com/npm/npm/pull/8668

1 files changed, 3 insertions, 3 deletions

diff --git a/lib/set.js b/lib/set.js
index c83602ec1..b5e7376fb 100644
--- a/lib/set.js
+++ b/lib/set.js
@@ -1,13 +1,13 @@
 
 module.exports = set
 
-set.usage = "npm set <key> <value> (See `npm config`)"
+set.usage = 'npm set <key> <value> (See `npm config`)'
 
-var npm = require("./npm.js")
+var npm = require('./npm.js')
 
 set.completion = npm.commands.config.completion
 
 function set (args, cb) {
   if (!args.length) return cb(set.usage)
-  npm.commands.config(["set"].concat(args), cb)
+  npm.commands.config(['set'].concat(args), cb)
 }