From b50be6aff34a739ca43de65f546e743d1a9975b9 Mon Sep 17 00:00:00 2001 From: Forrest L Norvell Date: Mon, 22 Jun 2015 22:18:52 -0700 Subject: 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 --- cli.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'cli.js') diff --git a/cli.js b/cli.js index 0df931e35..05c5e21fb 100755 --- a/cli.js +++ b/cli.js @@ -1,2 +1,2 @@ #!/usr/bin/env node -require("./bin/npm-cli.js") +require('./bin/npm-cli.js') -- cgit v1.2.3