Question 1

How do I use the globals package with ESLint?

Accepted Answer

For ESLint 8 and earlier, it's integrated by default. For ESLint 9, install it separately and reference it in your ESLint config's language options, as described in the README.

Question 2

What's the difference between globals.node and globals.nodeBuiltin?

Accepted Answer

globals.node includes CommonJS arguments like 'require', while globals.nodeBuiltin excludes them, useful for detecting accidental CommonJS references in ES modules, as explained in the README.

Question 3

How can I add a custom global variable to the globals package?

Accepted Answer

You cannot directly modify the package; instead, extend the globals object in your tool or create a custom set based on the existing JSON, since it's a static data file.

Question 4

Is globals package still necessary for ESLint 9?

Accepted Answer

Yes, but you need to depend on it directly. ESLint 9 no longer bundles it, so install it and configure it in your ESLint settings for environment-specific globals.

Question 5

Globals vs @types/node for TypeScript projects?

Accepted Answer

@types/node provides TypeScript definitions for Node.js APIs, while globals offers a list of global identifiers with read-only flags. Use globals for static analysis and linting, and @types/node for type checking in development.

Question 6

How to integrate globals with a custom static analysis tool?

Accepted Answer

Import the JSON file and use the globals sets to check for undefined variables or read-only violations. The simple structure makes it easy to incorporate into any analysis tool, as it's just key-value pairs.

ES and browser globals

What is ES and browser globals?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions