1564396449
详细说明: - 添加了V2版本的工作流页面和结果页面 - 更新了Serena记忆文件 - 添加了详细实施计划文档 - 优化了Vite配置 - 更新了项目文档CLAUDE.md - 构建了演示系统的dist版本 - 包含了exhibition-demo的完整依赖
1.6 KiB
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:
globals.nodeBuiltin: Globals available to all code running in Node.js. These will usually be available as properties on theglobalobject and includeprocess,Buffer, but not CommonJS arguments likerequire. See: https://nodejs.org/api/globals.htmlglobals.node: A combination of the globals fromnodeBuiltinplus all CommonJS arguments ("CommonJS module scope"). See: https://nodejs.org/api/modules.html#modules_the_module_scope
When analyzing code that is known to run outside of a CommonJS wrapper, for example, JavaScript modules, nodeBuiltin can find accidental CommonJS references.