Skip to content

Global identifiers from different JavaScript environments

License

Notifications You must be signed in to change notification settings

sindresorhus/globals

Folders and files

NameName
Last commit message
Last commit date

Latest commit

8a43ab6 · Feb 12, 2025
Feb 12, 2025
Feb 12, 2025
Dec 18, 2024
Jun 7, 2017
Jun 19, 2018
Feb 10, 2024
Nov 17, 2017
Dec 10, 2014
Feb 12, 2025
Jun 7, 2017
Feb 19, 2024
Mar 9, 2020
Feb 12, 2025
Sep 27, 2024
Jun 1, 2024
Oct 9, 2024
Feb 20, 2024

Repository files navigation

globals

Global identifiers from different JavaScript environments

It's just a JSON file, so you can use it in any environment.

This package is used by ESLint 8 and earlier. For ESLint 9 and later, you should depend on this package directly in your ESLint config.

Install

npm install globals

Usage

import globals from 'globals';

console.log(globals.browser);
/*
{
	addEventListener: false,
	applicationCache: false,
	ArrayBuffer: false,
	atob: false,

}
*/

Each global is given a value of true or false. A value of true indicates that the variable may be overwritten. A value of false indicates that the variable should be considered read-only. This information is used by static analysis tools to flag incorrect behavior. We assume all variables should be false unless we hear otherwise.

For Node.js this package provides two sets of globals:

When analyzing code that is known to run outside of a CommonJS wrapper, for example, JavaScript modules, nodeBuiltin can find accidental CommonJS references.