2311061106/frontend/node_modules/globals
23175 b8b09fd9d4
Some checks failed
autograde-final-vibevault / check-trigger (push) Successful in 13s
autograde-final-vibevault / grade (push) Failing after 55s
完成作业
2025-12-14 16:02:40 +08:00
..
globals.json 完成作业 2025-12-14 16:02:40 +08:00
index.d.ts 完成作业 2025-12-14 16:02:40 +08:00
index.js 完成作业 2025-12-14 16:02:40 +08:00
license 完成作业 2025-12-14 16:02:40 +08:00
package.json 完成作业 2025-12-14 16:02:40 +08:00
readme.md 完成作业 2025-12-14 16:02:40 +08:00

globals

Global identifiers from different JavaScript environments

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

This package is used by ESLint.

This package no longer accepts new environments. If you need it for ESLint, just create a plugin.

Install

npm install globals

Usage

const globals = require('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.