Skip to content
This repository has been archived by the owner on Jul 27, 2020. It is now read-only.

A list of confusing globals that should be restricted to be used as globals

License

Notifications You must be signed in to change notification settings

sidoshi/eslint-restricted-globals

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

eslint-restricted-globals npm npm

⚠️ This package is deprecated. Please check confusing-browser-globals instead which solves the same problem and is preferred over this package.

A list of confusing globals that should be restricted to be used as globals

Install

$ npm install --save eslint-restricted-globals

Some global variables in browser are likely to be used by people without the intent of using them as globals, such as status, name etc. And because eslint thinks of them as valid global variables, it does not warn in case of bugs.

For eg:

function foo(nama) {
    if (nama) {
        console.log(name)
    }
}

Here we try to log variable nama if it is truthy, but by mistake we are logging name and as name is a valid global, no eslint warning is shown.

To avoid this, we blacklist such confusing globals which are exported from this package. It contains the list of variables that we think should not be used without window. qualifier. But as this is just a javascript array you can add, remove variables or even make your own list of variables.

Usage

Add this in your eslint config in rules property:

var restrictedGlobals = require('eslint-restricted-globals')

module.exports = {
    rules: {
        'no-restricted-globals': ['error'].concat(restrictedGlobals),
    }
}

License

MIT

About

A list of confusing globals that should be restricted to be used as globals

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published