no-unused-vars behavior with global variables

When the scope is all, and you declare a global variable in one file:

// file1.js
myGlobal = 123;

but you only consume the variable in another file:

// file2.js
console.log(myGlobal);

ESLint doesn’t pass (because it’s only looking at each file individually). Since almost invariably global variables are used across files, this really reduces the utility of the all option.

Any chance ESLint can do a quick pass across all files first so it’s aware of global var definitions and usages? Thanks for the awesome project @nzakas !

[nzakas]

I’m sorry, this is very far outside the scope of what ESLint is meant to do and I don’t see addressing this. I think the best advice we can offer is that you build a tool that grabs global definitions from your files and outputs an eslintrc file with the globals predefined. Then, you can use extends to import it.

[qodesmith]

I was experiencing the same thing. I ended up just putting all the globals I was using inside the globals property within my .eslintrc.js file. The only drag was that each one had to be named individually like such:

'globals': {
  'var1': true,
  'var2': true,
  ...
}

Since each global is going to get a value of true anyway, would have been nice to be able to do it in an array like so:

'globals': {
  ['var1', 'var2', 'var3']: true
}