title: ESLint producing different output when run with npm run-script
body: <p>When I lint my code with <code>eslint scripts/**/*.js</code> I see two linting errors:</p>
  
  <pre><code>» eslint scripts/**/*.js
  /Users/user/dev/scripts/application.js
    3:8  error  "React" is defined but never used  no-unused-vars
  
  /Users/user/dev/scripts/components/Header.js
    24:2  error  Unnecessary semicolon  no-extra-semi
  
  ✖ 2 problem (2 error, 0 warnings)
  </code></pre>
  
  <p>That's fine. When I put that command into <code>"scripts"</code> in my <code>package.json</code> then I only get one error.</p>
  
  <pre><code>// package.json
  // ...
  "scripts": {
    "lint": "eslint scripts/**/*.js"
  }
  // ...
  
  
  » npm run lint
  /Users/david.tuite/dev/ui/scripts/components/Header.js
    24:2  error  Unnecessary semicolon  no-extra-semi
  
  ✖ 2 problems (2 errors, 0 warnings)
  </code></pre>
  
  <p>What's happening to the other linting error?</p>
  
  <p><strong>edit</strong>
  I'm starting to suspect this is a globbing problem. The missing linting error is in a file which isn't in a subdirectory of <code>scripts</code>.</p>