Update dependency globals to v17.9.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
globals	17.6.0 → 17.9.0

---

Release Notes

sindresorhus/globals (globals)

v17.9.0

Compare Source

v17.8.0

Compare Source

• Update globals (2026-07-01) (#​347) 7394811

---

v17.7.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[fossabot]

[fossabot]

✓ Safe to upgrade

I recommend merging this upgrade because it is a minor, additive version bump to a pure developer dependency with no breaking changes and zero impact on this project's codebase. The globals package is used exclusively in eslint.config.js to supply globals.node definitions to the ESLint linter — none of the changes in this release (which add new browser, worker, and AI/ML-related global definitions) touch the Node.js globals set the project relies on. The single included bug fix is a low-risk improvement, and no symbol changes were detected by static analysis. Because globals is scoped entirely to developer tooling with no runtime presence, this upgrade carries negligible risk.

What we checked

• The globals package is declared as "globals": "^17.6.0" in devDependencies, confirming it has no runtime presence — it is strictly a linting tool dependency. ^[1]
• The package is imported via require('globals') and its only usage is globals.node on line 11, which provides Node.js built-in global variable definitions to ESLint. The upgrade's new additions (browser, worker, CSS, DOM geometry, and AI/ML globals) are entirely irrelevant to this usage. ^[2]
• Usage is limited to { ...globals.node, VERSION: 'readonly', LICENSE: 'readonly' } — only the globals.node property is consumed. New globals added to browser and worker environments in this release do not affect this configuration at all. ^[3]
• The project requires Node.js >=20, and globals is a data-only package with no engine constraints, so there are no runtime compatibility concerns. ^[4]

Dependency Usage

The globals package is used exclusively within the project's developer tooling, specifically in eslint.config.js, where it supplies predefined Node.js global variable definitions to the ESLint linter configuration. Beyond that single file, the additional search confirms no runtime or application-layer usage — it is a pure developer dependency scoped entirely to code quality enforcement. This narrow, single-file footprint reflects a conventional linting setup pattern, where globals ensures the linter correctly recognizes built-in Node.js globals (alongside two custom project-level globals, VERSION and LICENSE) without raising false-positive warnings.

• The package is imported via require('globals') and its only usage is globals.node on line 11, which provides Node.js built-in global variable definitions to ESLint. The upgrade's new additions (browser, worker, CSS, DOM geometry, and AI/ML globals) are entirely irrelevant to this usage.
  

  minidrone-js/eslint.config.js

  Line 2 in 96a750d

  const globals = require('globals');

• Usage is limited to { ...globals.node, VERSION: 'readonly', LICENSE: 'readonly' } — only the globals.node property is consumed. New globals added to browser and worker environments in this release do not affect this configuration at all.
  

  minidrone-js/eslint.config.js

  Line 11 in 96a750d

  globals: { ...globals.node, VERSION: 'readonly', LICENSE: 'readonly' },

Changes

globals was updated with a build script fix and expanded browser/worker global definitions, including new AI-related APIs (LanguageModel, ModelContext, WebMCPEvent), DOM geometry types (DOMMatrix, DOMPoint, DOMQuad, DOMRect), off-screen rendering APIs (OffscreenCanvas, ImageBitmapRenderingContext), and the Temporal date/time API across browser, worker, and dedicated worker environments.

• Update globals (2026-06-22) (#345) 33b75f9 (v17.6.0-17.7.0, release notes)
• Fix build script (v17.6.0-17.7.0, commit)
• Update actions (v17.6.0-17.7.0, commit)

View 14 more changes

• Added CSSFontFaceDescriptors to browser globals - new CSS API for font face descriptor definitions (v17.7.0, package source)
• Added CSSPseudoElement to browser globals - support for CSS Pseudo-Elements API (v17.7.0, package source)
• Added LanguageModel to browser globals - new AI/ML language model API (v17.7.0, package source)
• Added ModelContext to browser globals - context support for AI language models (v17.7.0, package source)
• Added WebMCPEvent to browser globals - support for web MCP (Model Context Protocol) events (v17.7.0, package source)
• Added DOMMatrix and DOMMatrixReadOnly to browser globals - DOM geometry matrix API (v17.7.0, package source)
• Added DOMPoint and DOMPointReadOnly to browser globals - DOM geometry point API (v17.7.0, package source)
• Added DOMQuad to browser globals - DOM geometry quad API (v17.7.0, package source)
• Added DOMRect and DOMRectReadOnly to browser globals - DOM geometry rectangle API (v17.7.0, package source)
• Added ImageBitmapRenderingContext to browser globals - canvas rendering context for bitmap images (v17.7.0, package source)
• Added OffscreenCanvas to browser globals - off-screen canvas rendering API (v17.7.0, package source)
• Added QuotaExceededError to browser, worker, and dedicated worker globals - storage quota error handling (v17.7.0, package source)
• Added Temporal to browser, worker, and dedicated worker globals - new temporal date/time API (v17.7.0, package source)
• Updated puppeteer dev dependency from ^24.42.0 to ^25.1.0 (v17.7.0, package source)

References (4)

[1]: The globals package is declared as "globals": "^17.6.0" in devDependencies, confirming it has no runtime presence — it is strictly a linting tool dependency.

minidrone-js/package.json

Line 34 in 96a750d

"globals": "^17.6.0",

[2]: The package is imported via require('globals') and its only usage is globals.node on line 11, which provides Node.js built-in global variable definitions to ESLint. The upgrade's new additions (browser, worker, CSS, DOM geometry, and AI/ML globals) are entirely irrelevant to this usage.

minidrone-js/eslint.config.js

Line 2 in 96a750d

const globals = require('globals');

[3]: Usage is limited to { ...globals.node, VERSION: 'readonly', LICENSE: 'readonly' } — only the globals.node property is consumed. New globals added to browser and worker environments in this release do not affect this configuration at all.

minidrone-js/eslint.config.js

Line 11 in 96a750d

globals: { ...globals.node, VERSION: 'readonly', LICENSE: 'readonly' },

[4]: The project requires Node.js >=20, and globals is a data-only package with no engine constraints, so there are no runtime compatibility concerns.

minidrone-js/package.json

Line 10 in 96a750d

"engines": {

---

fossabot analyzed this PR using static analysis and dependency research. View this analysis on the web