Defining globals

[kmamykin]

I am working on a Appcelerator Titanium project, where the framework defines several globals that I would like to ignore.
Is there a suggested way to override them (through package.json for example) and keep using standard (instead of switching to eslint)?

[yoshuawuyts]

From the README:

How do I ignore files?

The paths node_modules/, .git/, *.min.js, bundle.js, and coverage/ are automatically excluded
when looking for .js files to style check.

Sometimes you need to ignore additional folders or specific minfied files. To do that, add
a standard.ignore property to package.json:

"standard": {
  "ignore": [
    "**/out/**",
    "**/lib/select2/**",
    "**/lib/ckeditor/**"
  ]
}

[kmamykin]

@yoshuawuyts you probably misunderstood my question. I am trying to ignore certain globals from generating standard's errors through some config setting. But I finally settled on explicitly specifying

/* global Titanium, Allow, arguments */

in each file.

[yoshuawuyts]

whoops, my bad.

[mattdesl]

Is there a resolution for this issue? I tend to work with APIs like ThreeJS, CocoonJS, PIXI, etc. which are often in global scope.

[maxogden]

@mattdesl I put /* global foo */ at the top of all my files, it's the simplest thing I can think of. Other than to not use globals :)